feat: add failed statuses for groups

[katrinan029]

Currently, the frontend lacks the data to show failed statuses from both Braze and internal API errors. This work introduces two new failed statuses, email_error and internal_api_error, and incorporates an additional field errored_at into the EnterpriseGroupMembership model.

Additionally, a new method has been implemented to allow for patch requests to the endpoint api/v1/enterprise-group/<group_uuid>/learners/. This method allows updating group membership records for email errors that occur in enterprise-access. That related PR can be found here: https://github.com/openedx/enterprise-access/pull/501

https://2u-internal.atlassian.net/browse/ENT-9040

Testing the endpoint locally

1. checkout both branches knguyen2/ent-9040 and https://github.com/openedx/enterprise-access/pull/501
2. create an enterprise group at http://localhost:18000/admin/enterprise/enterprisegroup/
3. create a group membership http://localhost:18000/admin/enterprise/enterprisegroupmembership/
4. from postman, send a patch request with body (raw) to http://localhost:18000/enterprise/api/v1/enterprise-group/<group_uuid>/learners/: { "learner": "edx@exampl.com", "status": "internal_api_error" }
5. confirm that the status was updated at the endpoing http://localhost:18000/enterprise/api/v1/enterprise-group/<group_uuid>/learners/

Merge checklist:

• [ ] Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
  • base.in if needed in production but edx-platform doesn't install it
  • test-master.in if edx-platform pins it, with a matching version
  • make upgrade && make requirements have been run to regenerate requirements
• [ ] make static has been run to update webpack bundling if any static content was updated
• [x] ./manage.py makemigrations has been run
  • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
  • Note: This must be run if you modified any models.
    • It may or may not make a migration depending on exactly what you modified, but it should still be run.
  • This should be run from either a venv with all the lms/edx-enterprise requirements installed or if you checked out edx-enterprise into the src directory used by lms, you can run this command through an lms shell.
    • It would be ./manage.py lms makemigrations in the shell.
• [x] Version bumped
• [x] Changelog record added
• [ ] Translations updated (see docs/internationalization.rst but also this isn't blocking for merge atm)

Post merge:

• [ ] Tag pushed and a new version released
  • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
• [ ] After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
  • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi. (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
• [ ] PR created in edx-platform to upgrade dependencies (including edx-enterprise)
  • Trigger the 'Upgrade one Python dependency' action against master in edx-platform with new version number to generate version bump PR
  • This must be done after the version is visible in PyPi as make upgrade in edx-platform will look for the latest version in PyPi.
  • Note: the edx-enterprise constraint in edx-platform must also be bumped to the latest version in PyPi.