Improves error when axis is missing/incorrect attributes

[jasonb5]

Description

Improves regrid2 error when axis is missing from dataset or has incorrect attributes.

• Closes [Feature]: Improve KeyError message when cf_xarray can't find CF attributes for coordinates with regrid2  #447

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

If applicable:

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass with my changes (locally and CI/CD build)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

[jasonb5]

I'd like to revisit this in the future and refactor regrid2 to use the newer xcdat axis functions to mitigate this issue all together.

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (44e0e3b) 100.00% compared to head (99400d6) 100.00%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@             Coverage Diff             @@
##              main      #481     +/-   ##
===========================================
  Coverage   100.00%   100.00%             
===========================================
  Files           14        28     +14     
  Lines         1425      2856   +1431     
===========================================
+ Hits          1425      2856   +1431     

Impacted Files	Coverage Δ
xcdat/regridder/regrid2.py	100.00% <100.00%> (ø)

... and 14 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[tomvothecoder]

One minor code suggestion, then LGTM.

[tomvothecoder]

There's some weird mamba error going on in the GH Actions build.

I'll take a look at it.

# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<

    Traceback (most recent call last):
      File "/usr/share/miniconda3/lib/python3.10/site-packages/conda/exceptions.py", line 1124, in __call__
        return func(*args, **kwargs)
      File "/usr/share/miniconda3/lib/python3.10/site-packages/conda_env/cli/main.py", line 78, in do_call
        exit_code = getattr(module, func_name)(args, parser)
      File "/usr/share/miniconda3/lib/python3.10/site-packages/conda/notices/core.py", line 109, in wrapper
        return func(*args, **kwargs)
      File "/usr/share/miniconda3/lib/python3.10/site-packages/conda_env/cli/main_update.py", line 132, in execute
        result[installer_type] = installer.install(prefix, specs, args, env)
      File "/usr/share/miniconda3/lib/python3.10/site-packages/mamba/mamba_env.py", line 55, in mamba_install
        index = load_channels(pool, channel_urls, repos, prepend=False)
      File "/usr/share/miniconda3/lib/python3.10/site-packages/mamba/utils.py", line 178, in load_channels
        repo = subdir.create_repo(pool)
    RuntimeError: Could not read JSON repodata file (/home/runner/conda_pkgs_dir/cache/47929eba.json) parse error line 593230: subdir mismatch

`$ /usr/share/miniconda3/condabin/mamba update -n xcdat_ci -f conda-env/ci.yml`

[jasonb5]

Nothing changed the conda-env files. I though it might be a caching issue so I restarted them last night. Guess that didn't clear it up, I might try restarting them again.

[jasonb5]

Guess this restart clear it up.

[tomvothecoder]

Yeah I tried restarting it a few times lol. You can merge if you are ready.

[lee1043]

I wonder if this improvement is going to be included for v0.6.0, which I hope so. Let me know if there is anything I can help on this PR.

[tomvothecoder]

I wonder if this improvement is going to be included for v0.6.0, which I hope so. Let me know if there is anything I can help on this PR.

Yes this will be included in v0.6.0 since it is a simple fix. We're just waiting on @jasonb5 to merge whenever he's ready.