Not all MARBL streams are archived

[mnlevy1981]

When running the test suite with a G1850MARBL_JRA compset, the h.bgc.z stream was copied to the baseline directory but the h.bgc.native stream was not. I was able to fix this with

diff --git a/cime_config/config_archive.xml b/cime_config/config_archive.xml
index 9ad34a9..f0f19b6 100644
--- a/cime_config/config_archive.xml
+++ b/cime_config/config_archive.xml
@@ -8,8 +8,8 @@
          h.(static|ocean_geometry)[._optional instance number].nc[.optional tile number] -->
     <hist_file_extension>h\.(static|ocean_geometry)(\._\d*)?\.nc(\.\d*)?$</hist_file_extension>
     <!-- match filenames of the form
-         h.bgc.*[._optional instance number].nc -->
-    <hist_file_extension>h\.bgc\..*?.?[_\d+]+.nc$</hist_file_extension>
+         h.bgc.[.optional stream name][._optional instance number].(date string).nc[.optional tile number] -->
+    <hist_file_extension>h\.bgc(\.\w+)?(\._\d*)?\.[-\d+]+\.nc(\.\d*)?$</hist_file_extension>
     <!-- match filenames of the form
          ic.(date string)[._optional instance number].nc[.optional tile number] -->
     <hist_file_extension>ic.[-\d+]+(\._\d*)?\.nc(\.\d*)?$</hist_file_extension>

(I just copied the comment and regular expression for the h.[optional_string] streams and added \.bgc between h and the optional instance number). PR coming soon, it seemed easier to create a new PR than add to #241

[mnlevy1981]

This is turning out to be a pretty complicated issue. I realized that the existing logic on main works fine for the short-term archiver, the problem is only that the test system is not copying the h.bgc.native to the baseline directory or trying to compare its contents. My proposed fix didn't actually address the issue at hand, I must have seen h.native and misread it to be h.bgc.native because I can't find the h.bgc.native file in any of my baseline directories. @jedwards4b suggests looking at CAM's config_archive.xml file, which has an entire <test_file_names> section that we do not have in this repo.

This doesn't look like it will be an easy or quick fix, so I'll look into it later -- I don't want to hold up the beta06 tag (or spend too much of my time on this issue right now)