add validation methods

[bj00rn]

Add methods for validation to support future implementation validation of parameters and api key in Home Assistant config flow in order to avoid creating broken sensors. To partially support home-assistant/core#106771

• validate api key (validation success not tested since I do not have an api key atm)
  -> (https://doc.forecast.solar/for_developers)
• validate plane -> (https://doc.forecast.solar/api:misc)

I had to add rate_limit and authenticate flags to _request method since /check endpoint does not provide rate limit headers in response and does not seem to exist behind authentication (at least not according to the docs)

[bj00rn]

home-assistant/core#106771

[bj00rn]

Seems that {api_key}/info endpoint does not provide code in response when 401 is returned for an invalid key, this causes an exception to be thrown in

forecast_solar/forecast_solar/exceptions.py

Line 29 in 171deff

super().__init__(f'{data["text"]} (error {data["code"]})')

when key is invalid. I've just tested with a nonsense key aaaaaaaaaaaaaaaa though som maybe results may vary depending if the key is well formatted or not.

Maybe it's worth into looking into cleaning up exception classes and defining arguments and not just passing data['message'] later on? Not sure what the pythonic way of doing this is though but passing arbitrary json to exception constructors should at least not throw another exception when keys are missing IMHO.

[bj00rn]

Depends on #43 for linting errors

[bj00rn]

@frenck @MartinHjelmare rebased now, tests are passing

[bj00rn]

@klaasnicolaas any chance of getting this merged soon? I Need this to resolve home-assistant/core#106771

[bj00rn]

@klaasnicolaas Thanks! Will you carve a new release with this fix?

[klaasnicolaas]

@bj00rn Yes, release v3.1.0 is now available.