Upgrade SQLAlchemy to 2.0.2

[emontnemery]

Proposed change

Upgrade SQLAlchemy to 2.0.2

https://docs.sqlalchemy.org/en/20/changelog/changelog_20.html#change-2.0.2

A workaround added to the tests until a release with sqlalchemy-utils including kvesteri/sqlalchemy-utils#677 is available.

Production testing:

• sqlite
• MariaDB
• postgresql

Performance testing

• neutral or slightly faster

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 #
• 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
• 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 issue.
• @home-assistant rename Awesome new title Change the title of the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign recorder Removes the current integration label and assignees on the issue, add the integration domain after the command.

[frenck]

Converted to draft, until SQLAlchemy 2.0.0 is released

[bdraco]

Hmm.. tests are passing locally

[bdraco]

postgresql looks good as well with the caveat that the dataset I'm using and the number of entities isn't as good as the mariadb/sqlite testing since I don't have a production install that uses postgresql, only a test one that has been running for a while with a smaller set of integrations.

[bdraco]

Testing is good on this. From my perspective this seems GTG now

[bdraco]

unmarking draft since 2.0.0 is out #86436 (comment)

[emontnemery]

Let's keep this as draft until a week after 2023.2 is released

[bdraco]

Sounds like a good idea. There is bound to be something that might conflict 👍

[bdraco]

Something is wrong with logbook queries. They are taking 10x longer than expected

[bdraco]

Its not this PR, its #87108

[bdraco]

Will merge tomorrow per previous discussion unless I hear otherwise.