Allow excluding fields from ncdata_check

[jimmielin]

Tag name (required for release branches): sima0_21_001
Originator(s): @jimmielin
AI tools used (if applicable; please also add the "AI-generated code" label to the PR):
What: claude-fable:5
How: Discussed the implementation, wrote most of the logic and tests.

Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):

• Allows excluding certain fields based on a .gitignore-like glob pattern from physics_check_data.
• This feature is expected to be used so ncdata_check_err=.true. can be turned on in tests that read multi-stage snapshots where some variables are explicitly intended to be ignored as they would not match.

Describe any changes made to build system: N/A

Describe any changes made to the namelist: host-side ncdata_check_exclude option - default empty

List any changes to the defaults for the input datasets (e.g. boundary datasets): N/A

List all files eliminated and why: N/A

List all files added and what they do: N/A

List all existing files that have been modified, and describe the changes:
(Helpful git command: git diff --name-status development...<your_branch_name>)

M       cime_config/namelist_definition_cam.xml
  - add ncdata_check_exclude

M       src/core_utils/string_core_utils.F90
  - pure core_glob_match and core_glob_list_excluded

M       src/physics/utils/phys_comp.F90
  - add &physics_nl ncdata_check_exclude

M       src/physics/utils/physics_data.F90
  - check_field_2d/3d/4d skip rows whose report label matches the exclusion list
  - write out the excluded list always so it is not a silent drop.

M       test/unit/fortran/src/core_utils/test_string_core_utils.pf
  - comprehensive tests for the added glob matching string utils.

M       test/fortitude.toml
  - silence nuisance trip for public accessibility on pfUnit .pf files

If there are new failures (compared to the test/existing-test-failures.txt file),
have them OK'd by the gatekeeper, note them here, and add them to the file.
If there are baseline differences, include the test and the reason for the
diff. What is the nature of the change? Roundoff?

All tests have expected NLCOMP failures due to the presence of the new ncdata_check_exclude namelist variable.

derecho/intel/aux_sima:

SMS_Ln9.ne3pg3_ne3pg3_mg37.F2000_C7.derecho_intel.cam-outfrq_se_cslam_analy_ic (Overall: FAIL)

• expected failure

derecho/gnu/aux_sima:

SMS_Ln9.ne3pg3_ne3pg3_mg37.F2000_C7.derecho_gnu.cam-outfrq_se_cslam_analy_ic (Overall: FAIL)

• expected failure

derecho/nvhpc/aux_sima (test is run via Github workflow. Only run the test manually if we need to save new baselines):

If this changes climate describe any run(s) done to evaluate the new
climate in enough detail that it(they) could be reproduced:

CAM-SIMA date used for the baseline comparison tests if different than latest:

[nusbaume]

Applied what would have been my change requests in the latest commit!

[peverwhee]

committed the one small comment change i had.