Users need a way to update Existing Collections.

This issue is intended as a starting point to document the needed changes.

Assumptions:

1. The STAC data would match the existing Collections Form Schema
2. Three API Endpoints would be accessible for the ingest-ui's nextjs backend to pass through requests (Get all, Get collection, Update collection)
3. Users could edit collections for any Tenant that they have access to via keycloak
4. Edit ingest and Edit existing collection share the same dataset:update permission in keycloak

A new age could be added to the VEDA Ingest UI under the Collections heading. From a Usability standpoint, it should be clear to the user that it is an existing collection and not a pending ingestion request:

From there, a user would need to see a list of existing collections. The app would need to get a list of all collections via a GET request. This could mirror the flow in the edit collection ingestion request. A list of collections for each tenant would be shown. Additional indication that a user is editing existing collections should be provided here.

Once selected, a second API Request should be made to GET the current data.

The existing CollectionIngestionForm component in edit mode would be able to display the data and allow users to edit via a RJSF or the JSON Editor view. Upon editing and validation, a PUT command would need to be made to update the data.