Don't write storage to disk while stopping

[dmulcahey]

Proposed change

This PR is a follow up to #33358 specifically this comment: #33358 (comment). The PR prevents storage from being written to disk while the HA state is CoreState.stopping. The changes account for 3 scenarios:

1. A delayed save is issued before HA stop event has fired and subsequently HA is stopped before the delay kicks in to issue the write
2. A delayed save is issued after HA stop event has fired
3. A save is issued after HA stop event has fired

In all of these scenarios the data is held in memory and written when HA is in the final_write state.

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

Example entry for configuration.yaml:

# Example configuration.yaml

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: RFC - Add a 3rd state to the HA shutdown sequence for writing data #33358
• 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.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

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

[dmulcahey]

I’ll look at the failure some more in the morning. I think there just needs to be a guard in the write data method...