Add an option to remove unphysical solutions data in the result object

[jdelpino]

Currently, unphysical branches are encoded with NaNs, but data about unphysical branches are kept. This is done in favor of plotting since NaNs are ignored. However, in problems where neither plotting (nor branch ordering) is important, storing unphysical branches seems an overkill. An option to sparsify data, in order to avoid storage of result objects filled with NaNs would be appreciated.

[oameye]

I agree. I already had I lot of annoyances with this. I propose we add a keyword to the transform_solutions function to filter the solutions of specific classes.

[jdelpino]

We should save by default physical solutions. We could then use simple Run-Length encoding to store the data: [https://en.wikipedia.org/wiki/Run-length_encoding]

[oameye]

Is filter_result! in the classification.jl file not what you want