Merge pull request openedx-unsupported#975 from openedx/jenkins/upgra…

…de-python-requirements-bfe46ec

Python Requirements Update

Merge pull request openedx-unsupported#975 from openedx/jenkins/upgra…

…de-python-requirements-bfe46ec

Python Requirements Update

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