HARMONY-1862: Update pystac library dependency

[vinnyinverso]

Jira Issue ID

HARMONY-1862

Description

This updates pystac compatibility by allowing you to use newer versions of pystac. This should allow you to use the latest version of pystac if using python 3.9 or 3.10.

Local Test Steps

Test a service (with local Harmony deployment):

1. Checkout branch HARMONY-1862 of this repo
2. If testing with harmony service example, also checkout branch HARMONY-1862 of the harmony service example repo
3. Build a service image using this branch of the service lib (see the service example README for instructions on building a service with a local copy/branch of the service lib).
4. Update your local Harmony instance service deployment to use the newly built image.
5. Run an example request and make sure it succeeds.

Standalone test:

1. Activate your virtual environment (python 3.9 or 3.10).
2. Run make install
3. Specify a newer version of pystac in your virtual environment (e.g. pip install pystac==1.10.1).
4. Run make test.

PR Acceptance Checklist

• Acceptance criteria met
• Tests added/updated (if needed) and passing
• Documentation updated (if needed)

[vinnyinverso]

Updated this because flake8 was mistaking the colon in http:// for a JSON-like colon.

[vinnyinverso]

Maybe should have an upper bound here? I want it to be flexible though because of all of the python versions we support.

[vinnyinverso]

Maybe should avoid the upper bound according to this:
https://iscinumpy.dev/post/bound-version-constraints/#tldr

Only add a cap if a dependency is known to be incompatible or there is a high (>75%) chance of it being incompatible in its next release. Do not cap by default - capping dependencies makes your software incompatible with other libraries that also have strict lower limits on dependencies, and limits future fixes. Anyone can fix a missing cap, but users cannot fix an over restrictive cap causing solver errors. It also encourages hiding issues until they become harder to fix, it does not scale to larger systems, it limits your ability to access security and bugfix updates, and some tools (Poetry) force these bad decisions on your downstream users if you make them.

related: nasa/harmony-py#79

[vinnyinverso]

This is just temporary until we move away from setuptools.

[vinnyinverso]

The latest version of pystac is not compatible with python 3.8, so we need some kind of range here to continue supporting python 3.8, 3.9 and 3.10.

[vinnyinverso]

(I originally had this pinned to the latest pystac version but realized it wouldn't work with python 3.8)

[vinnyinverso]

Not having an upper bound is consistent with the guidance from the article referenced here https://github.com/nasa/harmony-service-lib-py/pull/47/files#r1773854232.

[ygliuvt]

if the pystac version (>= 1.0.0) is incompatible with python 3.8, we should update the README and code comments to remove python 3.8 from supported python versions.

[vinnyinverso]

if the pystac version (>= 1.0.0) is incompatible with python 3.8, we should update the README and code comments to remove python 3.8 from supported python versions.

It should be compatible. Sorry if that wasn't clear.

[chris-durbin]

Tested out successfully after building the harmony-service-example image from the HARMONY-1862 branch.

[chris-durbin]

I think the whole .vscode directory would be good

[ygliuvt]

Tested successfully locally.