frontend-platform supports runtime configuration since 2.5.0 (see the PR
that introduced it[1], but it requires MFE cooperation. This implements
just that: by avoiding making configuration values constant, it should
now be possible to change them after initialization.
Almost all changes here relate to the `LMS_BASE_URL` setting, which in
most places was treated as a constant.
[1] openedx/frontend-platform#335
Refactor the locationId constant for the subdirectory-based
deployments support.
Exclude the MFE's `PUBLIC_PATH` from the constant.
The `window.location.pathname` example:
```
<PUBLIC_PATH>block-v1:oragrading+oragrading+oragrading+type@openassessment+block@ee217e897a954c1faa3b29317da0f2e7
```
Where the `PUBLIC_PATH` could be:
- `'/'` - for subdomain-based deployments (default)
- `'/mfe-specifix-public-path/'` - for subdirectory-based deployments
Changes
-------
- Bump frontend-platform to bring `intl-imports.js` script
- Move all i18n imports into `src/i18n/index.js` so `intl-imports.js` can
override it with latest translations
- Add `atlas` into `make pull_translations` when `OPENEDX_ATLAS_PULL`
environment variable is set.
- package.json and package-lock.json are copied from https://github.com/openedx/frontend-app-ora-grading/pull/176
- updated snapshots and updated tests in sync with `frontend-platform`
- require package-lock.json version 3: same as https://github.com/openedx/frontend-app-ora-grading/pull/176
Refs: [FC-0012 project](https://openedx.atlassian.net/l/cp/XGS0iCcQ) implementing Translation Infrastructure OEP-58.
The .github/workflows/add-remove-label-on-comment.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.
The .github/workflows/add-depr-ticket-to-depr-board.yml workflow is missing or needs an update to stay in
sync with the current standard for this workflow as defined in the
`.github` repo of the `openedx` GitHub org.
