Edit stac collections

[stephenkilbourn]

This will close #131 (Support Editing Existing Collections STAC Metadata) once the feature flag is cleaned up.

A feature flag must be set to "true" or else no changes are actually visible. For cleanup insructions, refer to FEATURE_FLAG_CLEANUP.md

Sidebar

The Sidebar has been updated to have a Collction Management and Dataset Management section. The new "Edit Collection Management" link was added. These routes are only accessible for users with appropriate permissions:

Collection Management Page

The Collection Management page shows cards and brief descriptions for each of the Edit types. If a user lacks keycloak access, the card is disabled and a tooltip instructs the user to request the appropriate permission. A similar tooltip was added for both Editing Collection Ingests and Dataset Ingests.

Diff Modal

This adds a diff modal to all Edit routes including the new edit collection one. This allows a user to more clearly see the requested changes prior to submission:

Edit Existing Collection Search view

Available collections are displayed via a new ExistingCollectionsList component. An api call is made to https://staging.openveda.cloud/api/stac/collections to determine existing collections. Users can narrow their search to tenants allowed via their keycloak seession via a dropdown. This adds the query parameter to the search: ?https://staging.openveda.cloud/api/stac/collectionstenant=SELCTED_TENANT

Edit Existing Collection View

Once a collection is selected, an api call is made to https://staging.openveda.cloud/api/stac/collections/COLLECTION_ID to retrieve their current STAC data and that is populated in a RJSF form. This reuses the existing Collection Ingest Edit form, but it adds a warning banner at the top and uses a new endpoint to save changes.