fix: Convert UUIDField columns to uuid type for Mariadb

[Ardiea]

Description

The behavior of the MariaDB backend has changed behavior for UUIDField from a CharField(32) to an actual uuid type. This is not converted automatically, which results in all writes to the affected columns to error with a message about the data being too long. This is because the actual string being written is a UUID with the - included, resulting in a 36 character value which can't be inserted into a 32 character column.

Supporting information

https://docs.djangoproject.com/en/5.2/releases/5.0/#migrating-uuidfield

Testing instructions

Configure edx-platform to use a MariaDB database as well as the work necessary to use Libraries V2 (meilisearch, etc), run the migrations up through the Django 5.2 update, then perform the 5.2 update and try to create a new V2 Library. It will error. After applying these migrations it should work.

Deadline

This is a blocking error that prevents the LibrariesV2 from being operational when using MariaDB as the database engine.

Other information

This is in addition to the migrations found in PR #37494

[openedx-webhooks]

Thanks for the pull request, @Ardiea!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[ormsbee]

I will review this, but please merge after #37924 (and rebase on top of it). I'm doing some migration squashing, and I'm worried that these two PRs are going to collide in a confusing way otherwise. Thank you.

[ormsbee]

I've just merged #37924. Please rebase onto the latest master, and remake this migration as migration 0016. Thank you.