Use separate data coordinators for AccuWeather observation and forecast (#115628)

* Remove forecast option

* Update strings

* Use separate DataUpdateCoordinator for observation and forecast

* Fix tests

* Remove unneeded variable

* Separate data coordinator classes

* Use list comprehension

* Separate coordinator clasess to add type annotations

* Test the availability of the forecast sensor entity

* Add DataUpdateCoordinator types

* Use snapshot for test_sensor()

---------

Co-authored-by: Maciej Bieniek <478555+bieniu@users.noreply.github.com>

homeassistant/components/accuweather/strings.json

@@ -11,7 +11,7 @@
       }
     },
     "create_entry": {
-      "default": "Some sensors are not enabled by default. You can enable them in the entity registry after the integration configuration.\nWeather forecast is not enabled by default. You can enable it in the integration options."
+      "default": "Some sensors are not enabled by default. You can enable them in the entity registry after the integration configuration."
     },
     "error": {
       "cannot_connect": "[%key:common::config_flow::error::cannot_connect%]",
@@ -790,16 +790,6 @@
       }
     }
   },
-  "options": {
-    "step": {
-      "init": {
-        "description": "Due to the limitations of the free version of the AccuWeather API key, when you enable weather forecast, data updates will be performed every 80 minutes instead of every 40 minutes.",
-        "data": {
-          "forecast": "Weather forecast"
-        }
-      }
-    }
-  },
   "system_health": {
     "info": {
       "can_reach_server": "Reach AccuWeather server",