Split august and yale integrations [part 1]

[bdraco]

Note that this PR is merging to yale_august_split

There are no code changes from august other than renames.

Proposed change

Yale and August have split into two separate companies and the APIs are diverging enough that the integration needs to be split into two.

Plan:

1. Copy the august integration to yale and change all the names. (this PR - Split august and yale integrations [part 1] #122253)
2. Replace config flow with Oauth (uses account link)
3. Replace pubnub push with the new websocket from Yale Global
4. Merge back to dev
5. Deprecate the old yale api calls from august

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: August integration non refreshing states #118474 Yale Home needs a Update Yales latest and all future Smart Alarm hub''s will only be visible in Yale Home #121964 Yale home needs an update  #108348 Yale home entities only refreshed when you open the Yale Home iOS app #103052 Yale Home - Global servers (via August integration) stop getting updates after a while #100798
• Link to documentation pull request: Split august and yale integrations home-assistant.io#33890

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 Ruff (ruff format 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.

To help with the load of incoming pull requests:

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

[home-assistant]

When adding new integrations, limit included platforms to a single platform. Please reduce this PR to a single platform

This is a copy, platforms are already reviewed

[MartinHjelmare]

There is still some use of "august" in the test fixtures.

[bdraco]

This is expected as the yale (company) code was forked from the original august code and they still have august all over the place internally. Even the yale locks you buy have august in the bluetooth firmware (although there are no references on the packaging or device)

[bdraco]

Its all super confusing. I'll try to summarize what I know but even some of this is based on discovery and patchwork information as even the people working at entities themselves don't seem to have the full story.

August was sold to ASSA ABLOY, and than the North American devices were spun off into yet another company "Yale August" aka august.

• The original august system is "dead".
• The yale integration will be for what the "ASSA ABLOY" company is doing. aka yale fork aka outside of North America. "ASSA ABLOY" is moving most/all of their existing integrations to this platform. Yale Doorman and other similar devices will only eventually be supported here. Push updates are currently broken here because the api is now websocket based.
• The august integration will be for what the "Yale August" company is doing. aka august fork aka North America. Assure2 locks and the Assume+ locks will only be supported here. The original August company devices are folding into Yale August. The august company is keeping the current pubnub based system for integrations at this time. They may move to another system but thats unknown at this point.