feat: DPS STAC user catalogs

[hrodmn]

This PR modifies the DpsStacItemGenerator behavior to do a few things:

• associates the collection with a user-specific Catalog in the DPS User STAC (creates it if the catalog doesn't exist yet)
• generates the boilerplate STAC collection document with a deterministic collection id ({username}__{algorithm_name}__{algorithm__version}) in the DpsStacItemGenerator handler (instead of delegating to stac-loader) but will use collection metadata provided by the user if it is present although the collection id still gets replaced with auto-generated id unless the collection is in the approved registry of named collections.
• a metadata migration script to generate the user catalogs for existing collections

The new DPS User STAC Browser (test deployment url https://dps-staca-browser.dit.maap-project.org) is configured to be browsed using the user catalog hierarchy. Here is the landing page:

Then all of the user's collections are visible within the catalog view:

Resolves #130
Resolves #131

[jjfrench]

oh, interesting - I thought this would break on 2.224 related to the IKeyRef > developmentseed/eoapi-cdk#218

[hrodmn]

yeah I'm not sure about that - maybe it was an incompatibility between aws-cdk and aws-cdk-lib? I had to upgrade because I hit this error: https://github.com/MAAP-Project/maap-eoapi/actions/runs/35442041957/job/105894415203