More updates for Intel oneAPI and consolidation of common/modules*.yaml

[climbfuji]

Summary

This PR contains the following changes:

1. Based on the functionality to merge modules_${LMOD_OR_TCL}.yaml with modules.yaml, strip out the common settings from moduels_lmod.yaml and modules_tcl.yaml and put them in modules.yaml.

2. Additional updates for building the full unified environment with the oneAPI C/C++ compilers:

   • Add gmake, libbsd, libm to modules exclude list
   • Currently only in the blackpearl site config (once this all works, it can be moved to common/packages_oneapi.yaml): build bison, gmake, libm, libbsd with gcc. That's because bison doesn't build with oneapi (it builds but produces garbage, see bison miscompiled with %oneapi spack/spack#37172)

3. In configs/templates/unified-dev/spack.yaml: exclude jedi-tools-env and ai-env for oneapi, similar to what's done for intel (this was also done in a previous PR, therefore just cleaning up the comments in the file).

With these changes, the unified environment builds with [email protected] with the exception of wgrib2 (see #967 and #1199)

Testing

• CI
• Blackpearl with oneapi and gcc

Applications affected

n/a

Systems affected

Nautilus and Blackpearl - these are the only sites that have oneapi compilers configured

Dependencies

• waiting on Remove unused options from "spack stack" extension and add logic to set compiler for "spack stack create env" #1192

Issue(s) addressed

More steps towards #912

Checklist

• This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
• These changes have been tested on the affected systems and applications.
• All dependency PRs/issues have been resolved and this PR can be merged.

[climbfuji]

@AlexanderRichert-NOAA I think this is ready for your review (and testing if inclined to do so)