Resolve polar coordinate handling in SolutionData

[Devin-Crawford]

Description of the current limitations

When get_solution_data() is used to retrieve data from a report, the post-processing may be applied inconsistently. In particular, a far-field report that is in polar coordinates having been generated by sweeping theta and phi must be rendered after data retrieval as cartesian. This inconsistency can be very confusing.

Code sample expected

There are multiple ways to resolve this issue. The most important thing to achieve here is self-consistency so that a report that has alredy been processed in polar coordinates retain that information after data is retrieved using get_solution_data()

Useful links and references

No response