Fix cast translations

[balloob]

Breaking change

Proposed change

Fix state translations for cache using two hacks:

• We cache the current version of Home Assistant in a variable so we can check if we're using a specific version without having access to hass object
• I made a copy of the old state translations for cast and they are merged into the translations when doing a build
• computeStateDisplay is now falling back to old behavior if Home Assistant is using a version before 109.
• Remove no longer used translation keys from source file

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

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.
• There is no commented out code in this PR.
• 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

[bramkragten]

Can we move this to a separate function?

[bramkragten]

  if (__BACKWARDS_COMPAT__ && !atLeastCachedVersion(0, 109)) {
	return legacyComputeStateDisplay(localize, stateObj, language);
  }

[balloob]

Done.