New configuration of maximum number of open chrome tabs

• New config value in [chrome] section to configure maximum number of open tabs in chrome to stabalize system. Recomended value for py 3 is in my case 5 tabs.
• Fix issue #9. logging in files is working again. Thanks for creating this issue!
• Fix some issues in the readme

Chrome Tab Handling optimized

• Optimized tracking of open tabs in chrome
• HA entity for disk usage changed (was wrong defined as batter type)
• HA icons added to discovery

New release including Home Assistant discovery

Fundamental changes in this new version.

Previous versions had the issue that each time a new panel or url was loaded a new tab was created in chrome. Over time you got more and more tabs. This slowed down the system more and more.
In the new version of the mqttDisiplayClient chrome is controlled over the DevToolsAPI of chrome.
You have control now how many tabs are created and of the lifetime of the tabs.

See the Readme.md how to enable DevTools API in chrome and how to configure chrome in the ini file.
check also the remarks how ro configure URLs for the panels in the ini file. This is important to control the tabs in chrome correctly.

Additional changes:

• Home Assistant discovery added
• All files are pylint conform. Because of this, all python files have pylint conform names now.
• The blank_page switch topic is removed. You can select a blank panel with the panel topic
• It you send a url to the url topic, the url is now imediately shown and the panal topic switches to URL
• Logger writes now also in a file. Location and name can e configured.
• url section in ini file removed
• chrome and haDiscover section added in ini file
• The client has now an integration test frame to verify the functionality

backlight control can be disabled

See also: #2

Change setup with -f option to enable optional features

V0.2

Another correction in the install description

Initial release

V0.1

Update installation description