Change persistence handling to standardize saving dictionaries as json in JsonUtil.encode_object

[ernstleierzopf]

For example like in the EFD:

for log_ev, freq in self.counts_prev.items(): persist_data.append((log_ev, freq))

[ernstleierzopf]

Idea: use the old pull request to create a concept of persisting data and adapt it at a per class basis.

[ernstleierzopf]

Also change persistence after creating new unittests - wait before a major release.

[ernstleierzopf]

ToDo after unittests for the analysis classes are created - always also check the persisted data format on disk. These are breaking changes and need to be done before a new release.

[ernstleierzopf]

save ETD data as dictionary.

[ernstleierzopf]

#300 is related.

[ernstleierzopf]

I think there will never be a good opportunity to implement this this issue, because these would be breaking changes for existing deployments. There could be an automatic tool to update existing persisted data, but it might not be worth the implementation time and risks involved. The benefits simply do not outweight the risks and hassle.

@landauermax do you agree?

[landauermax]

Yes I agree, it is high risk and not worth it just for the sake of standardization.