Pull FIELDS_JSON_URL into the codebase on release

[jsignell]

Related Issue(s):

• Runtime network loading of FIELDS_JSON_URL and mixed type enum #400

Description:

This PR adds a step to the release process that pulls the remote file and puts it in a particular location where it can be read from the pystac code and bundled up with the code when packaging.

I did not try to tackle the question of cleaning up the Enum because of the option to pass in custom fields. I don't see an easy way to clean this up without breaking backwards compat.

PR Checklist:

• pre-commit hooks pass locally
• 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-commenter]

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.05 ⚠️

Comparison is base (70788e1) 90.34% compared to head (bd3180d) 90.29%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1045      +/-   ##
==========================================
- Coverage   90.34%   90.29%   -0.05%     
==========================================
  Files          47       47              
  Lines        6213     6215       +2     
  Branches      929      929              
==========================================
- Hits         5613     5612       -1     
- Misses        422      424       +2     
- Partials      178      179       +1     

Impacted Files	Coverage Δ
pystac/summaries.py	78.88% <100.00%> (-0.89%)	⬇️

... and 1 file with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

[jsignell]

Phew 😅 that was a lot of fails in a row, but should be ready for review now.

[gadomski]

I took the liberty of updating the CHANGELOG. One note -- when #400 is closed by this PR, we should create an issue to capture the second part of @schwehr's ticket (mixed type enum). I'll update the PR description to include a checkbox for this task.

[jsignell]

we should create an issue to capture the second part of @schwehr's ticket (mixed type enum)

The reason for the mixed type enum is that there are mixed types in the original fields.json. So the enum is just smoothing over an oddity in the upstream definition. I don't really see how we can do anything about it in pystac itself as long as we still want to accept arbitrary fields json.

[gadomski]

LGTM ... I also re-added FIELDS_JSON_URL as a deprecated field, w/ a plan to remove in v2.

Because we're adding a new module, this is technically a feature-adding, backwards compatible change, so needs to be in v1.8. I'm going to hold off on merging until #1049 lands and we release v1.7.1.