Fix/oauth fail due to blocked user agent

[xernaj]

Fixes #142 #121

• Update an old user agent in header that was blocked so oauth token could not be retrieved
• OAuth bearer token must be in get calls (haven't tested posts/puts)
• HTTP 429 (rate limited) could possibly still occur due to the amount of retries and loops in the component. I think ring have enabled extra restrictions.
• linter fixes

Not done:

• oauth token should be cached rather than retrieved per call. This could potentially appear as an error in future.
• HTTP 429 check rather than adding a sleep() between retries

[coveralls]

Coverage decreased (-0.3%) to 63.241% when pulling 627a596 on xernaj:fix/oauth-fail-due-to-blocked-user-agent into 6d2368b on tchellomello:master.

[brama1966]

works perfectly

[tchellomello]

Hello @xernaj, thanks for jumping on this so quickly and providing a fix. Thanks also for all the community efforts as well.

@xernaj I've added some comments on your PR and please let me know what you think about it.

Thanks again for your help!!

[tchellomello]

Thanks @xernaj I've added some comments for the time.sleep(5) line, then it looks to be merged!

[tchellomello]

@xernaj after the pro tip review from the master @balloob, I want to apologize and ask if you want to create a new PR with the if statements you had before. I'm going ahead and merging this so we can have a hotfix in HA. @xernaj are you also planning to submit a PR to home assistant project?

[xernaj]

Thanks @tchellomello and @balloob, will look at a PR later for if changes though I don't see much value yet as it's a non functional change. As for PR for home assistant project, if someone else has the time, please go ahead, otherwise I can raise one in the next 24-48hrs.