update storage extension to v2.0.0

[tylanderson]

Description:

Updates storage extension to v2.0.0. Due to the major changes in v2, I have not attempted to make migrations from v1 to v2

StorageScheme platform property allows templated uri's, so arbitrary additional properties are allowed to be set on StorageScheme objects

PR Checklist:

• Pre-commit hooks pass (run pre-commit run --all-files)
• Tests pass (run pytest)
• 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

❌ Patch coverage is 91.54229% with 17 lines in your changes missing coverage. Please review.
✅ Project coverage is 92.21%. Comparing base (9bc7f70) to head (971cd7e).

Files with missing lines	Patch %	Lines
pystac/extensions/storage.py	91.14%	15 Missing and 2 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1561      +/-   ##
==========================================
- Coverage   92.22%   92.21%   -0.02%     
==========================================
  Files          55       55              
  Lines        8414     8538     +124     
  Branches      973      986      +13     
==========================================
+ Hits         7760     7873     +113     
- Misses        466      476      +10     
- Partials      188      189       +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]

I think we have unnecessary new extensions here ... both schemes and refs can just be classes, not extensions themselves?

[thomas-maschler]

Can you also add GCS = "gcp-gs"

[thomas-maschler]

generally, having parity to the v1 Enum would be great

[tylanderson]

I didn't see best practice GCP storage defined here, so did not add as a possible enum here, but as written schemes can be set to any string. I think opening a PR in the extension w/ a suggested schema to use for GCP storage would make sense before implemented here.

[gadomski]

Maybe I missed it, but we should test the migration path from v1 to v2.

[gadomski]

Looks like the docs need to be reverted back to a single class?

[pjonsson]

Missing closing brace.

[tylanderson]

Maybe I missed it, but we should test the migration path from v1 to v2.

I'm taking a look at what adding a migration hook would require, but I think there will be some cases that will be harder to migrate cleanly. (e.g. azure where we need account id, or the platforms that exist in v1 but not v2 e.g. IBM, alibaba)

[jsignell]

Maybe I missed it, but we should test the migration path from v1 to v2.

I'm taking a look at what adding a migration hook would require, but I think there will be some cases that will be harder to migrate cleanly. (e.g. azure where we need account id, or the platforms that exist in v1 but not v2 e.g. IBM, alibaba)

I think raising a warning in those cases and then leaving the data unchanged will be sufficient.