Adapt to latest FMS update and have an option to install DA-utils

[Dooruk]

This is taking care of multiple JEDI updates/issues:

1. Use FMS/2023.04 as a module #44

With this update, there is no need to copy mom6 and fv3 repos for soca and fv3-jedi builds anymore. These modules are linked via CMake instead.

Waiting on this https://github.com/JCSDA-internal/jedi-bundle/pull/103 to be merged first. merged

Second, this line is required in CMakelists.txt

list( APPEND CMAKE_INSTALL_RPATH ${CMAKE_CURRENT_BINARY_DIR}/fv3 )

Similar module updates will be done in SWELL for build method to work @asewnath GEOS-ESM/swell#395

2. add DA-utils as an optional repo #43

Now it is possible to build NOAA-EMC's DA-utils as an optional package (uses IODA and OOPS modules). It's a shared repo so we could contribute.

For this to be built, da-utils needs to be added in extra_repos and NOAA-EMC needs to be added to the github_orgs list in build.yaml.

3. saber depends on vader #45
   Build order change, saber depends on vader so vader gets built first: https://github.com/orgs/JCSDA-internal/discussions/143

4. pycodestyle version should be less than 2.12 #42

Some of this could use a documentation update...

[asewnath]

This is taking care of multiple JEDI updates/issues:

⚠️ one minor issue left, @asewnath when I run jedi_bundle I receive empty strings in the repo section of build.yaml, not sure if that is related to the pinned versions update?

I'm not sure what you mean by the repo section. Do you mean bundles? The pinned versions update had no changes to the default build.yaml other than appending the additional pinned_versions dictionary at the end. Can you post what the build.yaml looks like?

[Dooruk]

I had to add cloning a single file from a repo method, otherwise whenever any repo containing CMakelists.txt gets cloned, such as jedi-bundle, ecbuild tries to build it, rightfully so!

[asewnath]

I installed your branch and the build.yaml file I have after running jedi_bundle doesn't have the empty string issue. Was there something else I needed to do to recreate the empty string issue you're seeing?

[Dooruk]

I installed your branch and the build.yaml file I have after running jedi_bundle doesn't have the empty string issue. Was there something else I needed to do to recreate the empty string issue you're seeing?

Hmm, I'm testing it on SLES15. Let me install it on SLES12 and see.

[Dooruk]

I installed your branch and the build.yaml file I have after running jedi_bundle doesn't have the empty string issue. Was there something else I needed to do to recreate the empty string issue you're seeing?

You are right, reinstalled the repo and not receiving that bug anymore. Wish every solution was that simple!

So this is ready for testing/review, as long as the fv3-interface.cmake change is made after the cloning phase until the jedi-bundle PR is merged.