`fre.cmor`: be more flexible with CF compliant calendar input

[ilaflott]

i.e., if a calendar from the input data is e.g. noleap, then checking it against the requested calendar type from user config, noleap and 365_day should both be acceptable. currently though:

[ INFO:           cmor_mixer.py: rewrite_netcdf_file_var]     time_coord_units = days since 0001-01-01 00:00:00
[WARNING:           cmor_mixer.py:cmorize_target_var_files] finally, changing directory to:
/home/Ian.Laflotte/Working/fre-cli
[WARNING:           cmor_mixer.py:cmorize_all_variables_in_dir] !!!EXCEPTION CAUGHT!!!   !!!READ THE NEXT LINE!!!
[WARNING:           cmor_mixer.py:cmorize_all_variables_in_dir] exc=problem with rewrite_netcdf_file_var. exc=data calendar type noleap does not match input config calendar type: 365_day
exiting and executing finally block.
[WARNING:           cmor_mixer.py:cmorize_all_variables_in_dir] this message came from within cmorize_target_var_files
[WARNING:           cmor_mixer.py:cmorize_all_variables_in_dir] COULD NOT PROCESS: so/so...moving on
[WARNING:           cmor_mixer.py:cmorize_all_variables_in_dir] run_one_mode is True. breaking vars_to_run loop