update raster extension to v1.1.0

[pjhartzell]

Related Issue(s): #789

Description:

Makes "nan", "inf", and "-inf" valid values for the nodata property in raster:bands.

• update schema uri
• align the nodata type with the updated schema, which allows for numeric and "nan", "inf", and "-inf" strings.
• update tests and test data. For the test data, the raster:bands object added to the B09 asset is from the sentinel example in the Raster Extension repo.

PR Checklist:

• Code is formatted (run pre-commit run --all-files)
• 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

Merging #809 (31f072d) into main (1261e60) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #809   +/-   ##
=======================================
  Coverage   94.32%   94.33%           
=======================================
  Files          83       83           
  Lines       11885    11897   +12     
  Branches     1388     1389    +1     
=======================================
+ Hits        11211    11223   +12     
  Misses        495      495           
  Partials      179      179           

Impacted Files	Coverage Δ
pystac/extensions/raster.py	89.92% <100.00%> (+0.14%)	⬆️
tests/extensions/test_raster.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1261e60...31f072d. Read the comment docs.

[pjhartzell]

Thanks @gadomski for pointing me at #448. Beyond the relevant discussion on how to handle extension updates in the future, it looks like an extension hook should be added to this PR to conform to the current method of handling extension version updates.

[pjhartzell]

In this case, the only change between v1.0.0 and v1.1.0 is the allowance of certain strings for the nodata value. So updating STAC from v1.0.0 to v1.1.0 only needs the schema URI in the extensions_list to change from v1.0.0 to v1.1.0.

However, the migrate method is only called when stac_version differs from the current value. So adding an extension hook only migrates the URI if the imported STAC is <1.0.0.

[duckontheweb]

@pjhartzell Thanks so much for working on this, these changes all look good to me. Your comment on the migration only needing to update the schema URI is right on, so I think this is ready to be converted from Draft to PR and merged.

[duckontheweb]

@pjhartzell Any objection to me converting this from a Draft?

[pjhartzell]

No objection to convert from Draft. Thanks for taking a look.