Initial configuration of Codee Fortran formatter with examples (src/*.F90)

[climbfuji]

Initial configuration of Codee Fortran formatter with examples (src/*.F90).

This PR adds an initial .codee-format configuration file for the free Codee Fortran formatter and a temporary script run_codee_tmp.sh to get started with the tool (note that the day-to-day usage will be much simpler than in the script). The PR also demonstrates the effect of the formatting rules for the four Fortran source files in src/.

The goal of this PR is to provide the necessary information to decide on the formatting rules we want to use. Once we have agreed on the format, we can update the src/*.F90 files as needed and merge this PR. The integration with GitHub actions and the simplified usage on the command line will come after that. In a 3rd PR, we will work on a tighter integration of the codee format config with the capgen Fortran write to make sure that the auto-generated code also complies with the formatting rules.

The majority of the diffs are because NEPTUNE (and UFS) use two whitespaces as indentation, whereas the files in src/ currently use 3 whitespaces. We can change the codee config, but every space we save makes the lines shorter. To see the remaining differences, please select "Hide whitespaces" when looking at the files changed.

User interface changes?: No

Working toward #703

Testing: No changes to the tests - GitHub actions CI tests passed
test removed:
unit tests:
system tests:
manual testing:

[dustinswales]

@climbfuji Thanks for incorporating the code formatter here!
I love the idea, we just need to decide on a few details and incorporate this into our workflows.
As a github action, running the formatter could be invoked either diagnostically (report format violations) or prognostically (fix format violations).

[dustinswales]

@climbfuji Is the "free" suffix here to use "free formatted" version of Codee?

[climbfuji]

No, I had some logic in that script previously that would use this, it's no longer there because not needed.

Since the script won't be merged, I didn't bother taking this out.

[climbfuji]

Changed this to Preserve as per our discussion

[climbfuji]

I need to "unresolve" this conversation about whitespaces before/after colons. The argument was that these lines in CAM/SIMA are aligned for better readability. But this aligning doesn't just affect the white spaces before/after colons, but also before and after commas, parentheses, etc. See screenshot

Unless I change many of these SpacesAroundOperators to Preserve - which then defeats the purpose of using a formatter -, I'll get "unaligned" lines.

Going back to the previous comments and questions, "who is the audience"? The audience for the source code in ccpp-framework is ccpp-framework developers, not cam/sima scientists. I think it is ok to expect ccpp-framework developers to deal with non-aligned variable definitions in a handful of source files (and in auto-generated files, but these were never in question).

And, again, CAM/SIMA can do whatever it wants in their source code, independent on how we format ccpp-framework Fortran files.