Extend parsing of Scientific Notation to JSON capabilites

[maximilian-tech]

Solves Issues #1955 (comment) and #1952 (comment)

It boils down to yaml vs. json floating point parsing. The SafeLoader of yaml has to be extended to allow for the same range of float notations like json.
See here for more background.
I copied the SO-solution and it does work (for me)

This is needed to postprocess Fortran output as it often as a e (e.g. 1e-5)for scientific notation, which yaml does not accept, but json does accept.
And because the json schema input is parsed through a yaml loader, this notation is not accepted. This PR extends the yaml loader to accept json notation of scientific data representation.

[maximilian-tech]

@gaborbernat I rebased and added the CLI option --extend-yaml-scientifc-notation.

The current implementation uses a global variable, but this is the best solution I could come up with. Ideally the command line option is gone in the '1.0' release and with it this 'construct' so I think it is ok for now.

[gaborbernat]

Can you please add tests for the new features?

[maximilian-tech]

I added one test.

The pre-commit.ci bot does quite a lot of code changes I don't know how to prevent. This should probably be changed.

[maximilian-tech]

Is there anything I can do to aid the progress here? I need this to parse json schema which contains Fortran style scientific notation ( e.g. 1e-5) which is butchered by the yaml loader.

[gaborbernat]

CI Failing.

[maximilian-tech]

Yes, because the pre-commit bot breaks the code.

[gaborbernat]

Yes, because the pre-commit bot breaks the code.

You'll need to address that 🤔 by overriding the ruff checks causing the issue.