Better error message when link does not resolve

[jsignell]

Related Issue(s):

• closes Better error messages when a link is expected to resolve to a STAC object but doesn't #1482

Description:

Not sure if throwing a different error counts as a breaking change :)

PR Checklist:

• Pre-commit hooks and tests pass (run scripts/test)
• Documentation has been updated to reflect changes, if applicable
• This PR maintains or improves overall codebase code coverage.
• Changes are added to the CHANGELOG. See the docs for information about adding to the changelog.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.46%. Comparing base (bc5eae4) to head (363a313).
Report is 31 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1500      +/-   ##
==========================================
+ Coverage   91.44%   91.46%   +0.01%     
==========================================
  Files          54       54              
  Lines        7505     7509       +4     
  Branches      906      906              
==========================================
+ Hits         6863     6868       +5     
  Misses        457      457              
+ Partials      185      184       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gadomski]

Not sure if throwing a different error counts as a breaking change :)

Nah. Good thought, but bringing the error "in-house" by making it a STACError feels more like a bugfix to me :-P

Think this needs a changelog? Happy either way.