Create WeatherClient API resource and remove from config

[calvinmclean]

Description

This feature is a pre-requisite to some other features related to WeatherClient because it will assign an ID to the client.

Related features:

• Implement oauth flow for Netatmo WeatherClient instead of requiring all secrets #78
• Add another implementation of Weather Client using publicly-available weather API #65
• Add support for temperature/humidity sensors #49 (kind of?)

Requirements

• Use same format as the current configuration
• Located on the root path of the API
• Assign and ID and "display name" to the clients
• Research and create issue for secure credential storage, but initial implementation will just store in YAML
• This will not affect SoilMoistureControl because that is tied to a physical garden-controller and should only work with Zone's in a Garden with moisture sensors
• Netatmo client should update and save access_token and refresh_token when using refresh token
• Implementation details:
  • WeatherControl now needs to reference a WeatherClient's ID
  • Remove from config
  • Add yaml and json tags to structs
  • Implement in CRUD in StorageClient
  • Add API CRUD endpoints
  • Add Validate method to WeatherClient so Options can be validated for specific clients create endpoint will initialize the client which should verify if it is valid
  • Add /test endpoint or something similar to test weather client configuration/auth
  • Add configmap storage client
  • OpenAPI specification and docs
  • testing