Make offline 1850 compsets closer to when coupled to CAM by using CO2 from datasets rather than hardcoded values

[ekluzek]

In doing #3800 I noticed that when coupled to CAM we use CO2 from CAM, but for offline 1850 simulations we use a hardcoded value. In order to make these more likely to be synchronized we should change it so that we use CO2 datasets from DATM for 1850 (probably do the same for 2000 as well). Obviously for fixed dates these aren't likely to be very different. But, they are more likely to be updated when using datasets and we are trying to check that the datm datasets correspond reasonably closely to what CAM is using.

There is an inherent difference for CAM as they are using a dataset with 360 latitudes with monthly data, and we'll be using a single global value for CMIP7 that's yearly.

[wwieder]

Seems like this is a good idea, should we do this when we turn on CMIP7 data by default?
Note, I'm not worried about matching CAM's higher dimensioned (lat x month) approach and suggest we stick with an annual global value for simplicity.