Auto repair incorrect collation on MySQL schema

[bdraco]

Proposed change

As we do more union queries in 2023.5.x if there is a mismatch between collations on tables, they will fail with an error that is hard for the user to figure out how to fix

Error executing query: (MySQLdb.OperationalError) (1271, "Illegal mix of collations for operation UNION")

This was reported in the #beta channel and by PM from others so the problem is not isolated to a single user.

Since we never enforced this in earlier versions its likely some tables will have a mix of utf8mb4_unicode_ci and utf8_general_ci, and utf8mb4_general_ci as they were created with whatever the user's system default were. If they are not all utf8mb4_unicode_ci the unions data between tables with non-like collations will fail.

https://discord.com/channels/330944238910963714/427516175237382144/1100908739910963272

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes mariadb write error when tables are now all setup with utf8mb4 #75126 fixes Unhandled database error with MySQL: Illegal mix of collations #74293 fixes Illegal mix of collations (utf8mb4_unicode_ci,IMPLICIT) and (utf8mb3_general_ci,COERCIBLE) for operation '='" #79867 fixes Illegal mix of collations in MySQL recorder on 2022.7 #74634 fixes Multiple errors related to sqlalchemy: Illegal mix of collations #74230 fixes MariaDB - Illegal mix of collations for operation 'UNION' - Logbook won't load #73235
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (recorder) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of recorder can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign recorder Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[bdraco]

If that test doesn't work with 10.3/10.6 I'll have to do the longer CONVERT TO. It will make the test just a tiny bit slower

[bdraco]

The problem with 10.6/10.3 was that older versions return '' for the collation if it matches the server default so we have to check the server default