UnphiMojo must optimize XMIR files too

[yegor256]

At the moment, the result XMIR's coming out of UnphiMojo contain method attributes. Let's make sure they don't.

[yegor256]

@maxonfjvipon please, help with this one, it's pretty urgent, it blocks objectionary/eo-phi-normalizer#3

[yegor256]

@maxonfjvipon I believe, we should introduce a new unit test, which will take some .eo program, parse it to .xmir (using ParseMojo + OptimizeMojo) and then print the XMIR with the help of XMIR class from eo-parse. Then, it will take the XMIR and transfer it to .phi (using PhiMojo), then to .xmir (using UnphiMojo), and then print it with the help of the same XMIR class from eo-parse. The two printed EO programs must be the same, I believe.

[maxonfjvipon]

@yegor256 in most cases they will be different:
EO:

[x] > main
  x > y

XMIR:

<o name='main'>
  <o name='x'/>
  <o name='y' base='x' ref='...'/>
</o>

phi:

{main -> [x -> ∅, y -> ξ.x]}

unphi:

<o name='main'>
  <o name='x'/>
  <o base='$'/>
  <o name='y' base='x' method=''/>
</o>

[yegor256]

@maxonfjvipon OK, let's make this test:

• EO to XMIR (via ParseMojo + OptimizeMojo)
• XMIR to PHI (via PhiMojo)
• PHI to XMIR (via UnphiMojo)
• XMIR to EO (via XMIR)
• assert that EO is parseable (via ParseMojo)

[0pdd]

@yegor256 the puzzle #2737 is still not solved.

[0pdd]

@yegor256 the only puzzle #2737 is solved here.

[0pdd]

@yegor256 the puzzle #2750 is still not solved; solved: #2737.

[yegor256]

@rultor release, tag is 0.34.2

[rultor]

@rultor release, tag is 0.34.2

@yegor256 OK, I will release it now. Please check the progress here

[rultor]

@rultor release, tag is 0.34.2

@yegor256 Done! FYI, the full log is here (took me 32min)

[0pdd]

@yegor256 2 puzzles #2779, #2780 are still not solved; solved: #2737, #2750.

[0pdd]

@yegor256 the puzzle #2779 is still not solved; solved: #2737, #2750, #2780.

[0pdd]

@yegor256 all 4 puzzles are solved here: #2737, #2750, #2779, #2780.