feat: add API endpoint to retrieve secured Algolia API key for an EnterpriseCustomer

[adamstankiewicz]

Ticket: ENT-10079

Adds a new API GET /api/v1/enterprise-customer/<enterprise_uuid>/secured-algolia-api-key/ to return the following response structure:

{
  "algolia": {
    "secured_api_key": "...",
    "valid_until": "2025-02-28T12:00:00Z"
  },
  "catalog_uuids_to_catalog_query_uuids": {
    "catalog_uuid_1": "catalog_query_uuid_1",
    "catalog_uuid_2": "catalog_query_uuid_2"
  }
}

When using this secured Algolia API key to filter Algolia search results for all content available to an enterprise customer, no additional client-side filters are needed to be passed as the generated secured Algolia API key itself baked in filtering search results by any CatalogQuery associated with the customers' EnterpriseCatalog records.

By default, this secured Algolia API key is valid for 1 hour, though it is configurable via the Django setting SECURED_ALGOLIA_API_KEY_EXPIRATION. The expiration is returned as an ISO timestamp.

Also included in this API response is a mapping of EnterpriseCatalog uuids to their associated CatalogQuery uuids. These mappings would be used by frontends when further filtering down all content available to the enterprise customer to a specific catalog, i.e.:

• Determine enterprise catalog UUID associated with a subsidy (e.g., subscription license).
• Find catalog query UUID associated with the above enterprise catalog UUID (discerned through these mappings).
• Add additional filter on the frontend for the found catalog query UUID.

Post-review

• Squash commits into discrete sets of changes
• Ensure that once the changes have been deployed to stage, prod is manually deployed

[iloveagent57]

This is great, couple of minor suggestions!