chore: Upgrade MFEs to Node 16 (openedx-unsupported#930)

chore: Upgrade MFEs to Node 16 (openedx-unsupported#930)

chore: Upgrade MFEs to Node 16 (openedx-unsupported#930)

fix: move `frontend-app-learning` to release section (openedx-unsuppo…

…rted#881)

It is part of the Maple release and thus should be pulled
from the open-release/maple.master branch.

fix: move `frontend-app-learning` to release section (openedx-unsuppo…

…rted#881)

It is part of the Maple release and thus should be pulled
from the open-release/maple.master branch.

chore: upgrade coursegraph's neo4j image from 3.2 to 3.5 (openedx-uns…

…upported#824)

This coincides with our upgrade of Neo4j in
edx/configuration.

Other notes:
* We are specifically pinning 3.5.28 (instead of simply
  3.5) to ensure that we're using the exact same patch
  release as what's deployed from edx/configuration.
* In the provisioning script, we now specifically start lms
  and then `exec` the management command. Before, we
  used the `run` command, which started lms automatically.
  This worked; however,  it would create a *second* lms
  container if one was already running, which was very confusing.
  With this change, we will either (a) start a new lms container
  and use it, or (b) use the existing lms container.

TNL-8386

Merge pull request openedx-unsupported#811 from edx/lilac-or-bot-patch

build: add edx-community-bot workflow

Merge pull request openedx-unsupported#811 from edx/lilac-or-bot-patch

build: add edx-community-bot workflow

feat: Skip large-set warning if DEFAULT_SERVICES is overridden (opene…

…dx-unsupported#723)

Some developers make use of the option of overriding `DEFAULT_SERVICES` in
options.local.mk (a git-ignored overrides file) as mentioned in the docs.
These people presumably know what they're doing and have already selected
a smaller set of services, so there's no point in bothering them with a
warning.

Add instructions on how to enable comprehensive theming for devstack.

This is an effort to resolve https://discuss.openedx.org/t/enable-comprehensive-theming-devstack-mako-template-overrides-not-working/3557 post. Instead of enabling comprehensive theming by default in the devstack environment these instructions have been provided.