Fix failing CI tests (CRTM cmake errors) and remove dependency on w3nco

[climbfuji]

Description

1. Use tag v3.1.0-skylabv7 for CRTM until problems with recently introduced plain cmake build are resolved
2. Remove dependency on w3nco (replaced by w3emc); for more details see associated PR https://github.com/JCSDA-internal/fv3-jedi/pull/1127

Note. Once https://github.com/JCSDA-internal/fv3-jedi/pull/1127 is merged, need to revert the temporary branch name change for fv3-jedi

Issue(s) addressed

Resolves failing CI tests

This is a workaround for #49 (not a solution)

Dependencies

• waiting on https://github.com/JCSDA-internal/fv3-jedi/pull/1127

Impact

n/a

Checklist

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have run the unit tests before creating the PR: https://github.com/JCSDA/ufs-bundle/actions/runs/7675916463/job/20922782524?pr=48

[climbfuji]

@shlyaeva can you take a look at this PR when you have time, please?

@eap - FYI This PR was approved by Ben J beforehand, but the approval was dismissed when I pushed the latest commit.

[shlyaeva]

@climbfuji can you explain in a few words why this only affects ufs-bundle but not jedi-bundle? (or does it also affect jedi-bundle?)

[climbfuji]

@climbfuji can you explain in a few words why this only affects ufs-bundle but not jedi-bundle? (or does it also affect jedi-bundle?)

I can: I have no idea. But I assume it's because of the way we build the code - that whole mix and match of ecbuild packages for most packages, plain cmake for crtm, cmake external project for ufs-weather-model, is a fragile configuration. Going back to the release tag where crtm was an ecbuild package works. In jedi-bundle, we don't have all of that.

[shlyaeva]

@climbfuji sounds good to me, thank you!