Execute hc login on first run

[saveriol]

This PR aims to execute hc-login.py directly on first run of home assistant add-on. Two new text inputs has been added to HA addon configuration (HC email & password) and will be passed to hc-login.py.

Resolves:

• exec hc-login.py in run.sh if first run #53
• HomeAssistant addon #79 "Mqtt sppecial characters for passwords are not recognised - for instance $$ is converted to 1." as now the options are parsed using recommended bashio and this issue is fixed.

Notable changes

• bashio is used instead of jq to parse options in run.sh. I don't know if jq is used elsewhere, if not we will need to remove it in dockerfile (bashio is recommended in HA addons documentation)
• now the addon_config is mapped also, and in configuration will use this path by default instead of /share/ which I currently left there but I think we will need to remove it any time soon. Use addon_config is best practice on HA addons for a use case like this one. Also, this is included in add-on backups unlike /share/.
• hc-login.py does not print devices.json on stdout, instead an arg for the filename has beed added to the script so that the errors will be printed on stdout (and so, in the addon logs) instead of the file. Also, now it prints the discovered devices' names and hostnames in stdout so they can be seen in addon's logs.

[pmagyar]

Looks good to me. Maybe you really can remove jq from the docker file. My search result said, that we does not use it elsewhere.
The step to bashio is also great. Thanks for that!

[Meatballs1]

Haven't had a chance to test yet, would be good practice to validate the checksum on the dependency download in docker

[saveriol]

Maybe you really can remove jq from the docker file. My search result said, that we does not use it elsewhere.

I just checked and it's used in bashio. So we need to keep it.