Improve integration mapping chain resolution

[danielpgross]

tl;dr

Improves integration integration mapping chain resolution:

• Fixes behaviour for non-consecutive chained mappings
• Improves error messaging

Changes

#517 introduced automatic resolution of integration mappings to the current taxonomy, taking into account all newer mappings.

While working on #525, we discovered a flaw in that behaviour: subsequent mappings were only taken into account if they appeared in the next immediate version, but not versions after that. For example, 2022-02 would take into account mappings from 2024-07, but not 2024-10.

We also discovered that in case a category fails to be resolved through this process, the error message is cryptic and not actionable.

This PR:

• Changes the resolution algorithm to check all subsequent versions, not just the immediate next one
• Adds a check for resolution failure, raising a clear error
• Greatly improves unit tests to ensure non-consecutive mapping cases are covered

[danielpgross]

• Improve integration mapping chain resolution #526 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[danielpgross]

Merge activity

• Jan 10, 11:37 AM EST: A user started a stack merge that includes this pull request via Graphite.
• Jan 10, 11:41 AM EST: A user merged this pull request with Graphite.