Bugfix for registry variables with dimensions that are themselves registry variables

[peverwhee]

Tag name (required for release branches):
Originator(s): peverwhee, jimmielin

Description (include the issue title, and the keyword ['closes', 'fixes', 'resolves'] followed by the issue number):
Bugfix for dimensions that are defined in the registry and then used to allocate a different registry variable.

Describe any changes made to build system:

M    src/data/generate_registry_data.py
- use the local name for allocating dimensions defined in the registry (but use standard name for metadata)

Describe any changes made to the namelist: n/a

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:

A  test/unit/python/sample_files/physics_types_self_ref_dim.F90
A  test/unit/python/sample_files/physics_types_self_ref_dim.meta
A  test/unit/python/sample_files/reg_good_self_ref_dim.xml
- add new test that exercises dimension handling

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

M   test/unit/python/test_registry.py
- add new test that exercises dimension handling

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?

derecho/intel/aux_sima: all b4b, except expected NLFAIL for multitape

derecho/gnu/aux_sima: all b4b, except expected FAIL for FADIAB

derecho/nvhpc/aux_sima: run through workflow - b4b

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]

Thanks @peverwhee!

[jimmielin]

Thanks @peverwhee!