Remove sqlalchemy lambda_stmt usage from history, logbook, and statistics

[bdraco]

Proposed change

It looks like these need a bit more time to mature upstream per
sqlalchemy/sqlalchemy#8098 (comment)
so let's rip them out any place where we need to worry
about thread safety.

There will likely be another sqlalchemy bump for
sqlalchemy/sqlalchemy#8098 in the future
as that problem seems to be more generic. Its likely that problem will
present as a raised exception failure state. All evidence suggests that
the lambdas have another undiscovered different thread safety
issue since the proposed fix there didn't solve the inconsistencies with the lambdas.

I left them in purge and the recorder thread because the problems
are thread safety issues and these queries are always single threaded
and I didn't want to risk causing a regression of #71015

While this will make the queries slower, slower and correct
is better than fast and incorrect.

Likely fixes #65499
Likely fixes #70011
Fixes #73155
Fixes #72991
Fixes #73154
Fixes #73108
Fixes Limych/ha-average#139

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)
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[probot-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!
_{^{(message by CodeOwnersMention)}}

[probot-home-assistant]

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

[bdraco]

Testing

• sqlite
• mysql
• postgresql