Implement CRUD GUI for STAC Catalogs, Collections, and Items, Including an Asset Uploader

### Background
STAC (SpatioTemporal Asset Catalog) provides a standardized way to describe geospatial information, facilitating the discovery and usage of spatial assets. In the eoAPI project, we need to manage STAC catalogs, collections, and items effectively. A few end-users have specifically requested this functionality, emphasizing the need for user-friendly interactions with STAC components. In most cases, we actually want to avoid having manual operations

### Issue
We require a user-friendly interface to perform CRUD operations (Create, Read, Update, Delete) on STAC catalogs, collections, and items, and to load the underlying referenced assets of a STAC item based on the minimum use case described in [issue #5](https://github.com/developmentseed/eoAPI/issues/5).

### Requirements

The initial scope discussed with @batpad only addressed the **Update** capabilities, but it would be great to have a more complete tool to manage STAC catalogs visually.

1. **Create**:
- Implement forms to create new STAC catalogs, collections, and items.
- Validate the user input according to the STAC specification.
- Provide user feedback on successful creation or errors.

2. **Read**:
- Display existing STAC catalogs, collections, and items.
- Allow filtering and sorting based on various criteria.
- Include pagination for large datasets.

3. **Update**:
- Enable editing of existing STAC catalogs, collections, and items.
- Validate changes according to the STAC specification.
- Provide user feedback on successful updates or errors.

4. **Delete**:
- Implement the functionality to delete STAC catalogs, collections, and items.
- Include confirmation dialogs to prevent accidental deletions.
- Provide user feedback on successful deletions or errors.

5. **Asset Uploader**:
- Implement a GUI data uploader to load the underlying referenced assets of a STAC item.
- Follow the minimum use case based on [issue #5](https://github.com/developmentseed/eoAPI/issues/5).
- Ensure compatibility and smooth integration with the existing CRUD operations.

#### Additional Considerations
- Consider how we would manage authorization and authentication (ongoing conversation #3)
- Versioning - Can we track changes to a catalog
- Integration with upstream data workflow - how can we create a cohesive process with any upstream processes?
- Limitations on potential operations for data uploader and metadata ingestion (#65, #5 )
- Consider how the tool would fit into the demo application or complement it (#117 )
- Consider providing bulk operations for efficiency.
- Ensure that the GUI is responsive and accessible.