chore: optimize lms and cms resource limits

Description

Optimises CPU/Memory requests for the LMS and CMS.

The numbers are based on an OVH instance running with 2 CPU cores and 8GiB of RAM.

• The CPU limit for the LMS and CMS is updated to 1 core.
• The HPA for both the LMS and CMS is set to kick in at about 75% CPU used. The HPA is based on CPU Request rather than CPU limit, so eg. for the CMS calculated at 300% * 0.25 core.
• Worker memory limit is increased substantially. We aim for 2GiB by default.

These changes have been deployed to https://es1.kgdocluster.opencraft.hosting/ with the previous values deployed to https://es2.kgdocluster.opencraft.hosting/ gitlab repo

See below screenshot of running an import of the same course on both instances.

Testing instructions

• Log on to https://es1.kgdocluster.opencraft.hosting/
• Import a course.
• Verify on Grafana that when importing a course, memory use doesn't spike.
• Verify that the hpa values are set correctly with kubectl get hpa -nes1 and kubectl get hpa -nes2

Checklist

If any of the items below is not applicable, do not remove them, but put a check in it.

• Git commit history is clean
• Git commits are following conventional-commit practices
• Unit tests are added/updated
• Documentation is added/updated

Additional context

Add any other context about the merge request here.