Add support for streaming (push) history

[bdraco]

frontend: home-assistant/frontend#15112

Proposed change

Currently we poll for history data; like logbook we can stream this data to avoid database overhead. This change will allow us to update the frontend places that use cached-history so we can drop it. This change stems from the discussion in home-assistant/frontend#12873 (comment)

This will fix all the dropped states issues we have with cached history since commits are not instant. Currently we assume the data is always there after 1s (default commit interval) but its not always there since the backend API makes no guarantee about when the data will be available (we could be processing stats, or doing a purge, etc) so we tend to drop values which results in lots of unexplained history issues. This implementation can completely replace the cached history used on the frontend and it will never touch the database after the first queries to catch up.

Cc @agners I think this is the last piece we need before we can bump the commit internal to 3s (maybe 5s) and finally realize some more of the IO and flash lifetime savings from your testing

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 (history) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of history 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 history Removes the current integration label and assignees on the issue, add the integration domain after the command.

[balloob]

<3