feat: fetching of a secured Algolia key [BB-8083][BACKPORT]

[0x29a]

Description

This is a backport of #1.

I tested the original version with Nutmeg, and it doesn't work well. There were random re-renders on opening the profile dropdown and other issues, like requests to non-existent endpoints. That's why the target branch, opencraft-release/nutmeg.2, is based on openedx@04c0ea3, which was added 11 April 2022, because 3.42.5 version of edx-enterprise was released 7 April 2022. It's worth to mention that Palm version of this MFE runs much smoother than this one.

Testing steps

Testing steps are very similar to those for #1, just replace palm with nutmeg whenever it occurs and use 0x29a/bb8083/per-user-algolia-key-nutmeg instead of 0x29a/bb8083/per-user-algolia-key branches.

Also keep in mind these pitfalls:

1. Unlike Palm, Nutmeg devstack doesn't start Redis automatically. Additionally to make dev.up.large-and-slow, you'll have to run make dev.up.redis.
2. There is no CONTENT_PRODUCT_SOURCE_ALLOW_LIST in enterprise_catalog/apps/catalog/constants.py. You can skip this and other source-related steps.
3. Provisioning of enterprise-catalog may fail due to an ensurepip issue. In this case, edit Dockerfile to install python3-venv (there is python3.8-venv, but it doesn't work for some reason).
4. MySQL for enterprise-catalog may be crashing during provisioning. If you experience this, add the following change to docker-compose.yml:

    services:
      mysql:
        image: mysql:5.7
   +    command: ["mysqld", "--character-set-server=utf8mb3", "--collation-server=utf8mb3_general_ci"]
        container_name: enterprise.catalog.mysql
        environment:
          MYSQL_ROOT_PASSWORD: ""
          MYSQL_ALLOW_EMPTY_PASSWORD: "yes"
          MYSQL_DATABASE: "enterprise_catalog"   

[Agrendalath]

👍

• I tested this: compared the diff to the original PR; it's not a clean backport, but looks good
• I read through the code
• I checked for accessibility issues: n/a
• Includes documentation: n/a
• I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository: n/a