Refactoring the Tado Classes.

[Moritz-Schmidt]

Description

Refactoring the Tado Classes by creating a common base class. The base class contains all functionality which hasn't changed from the pre Tado X API to Tado X API and enforces compatible typing and naming between versions.
This also reduces duplicated code and improves typing.

---

Related Issues

Link any related issues that this pull request resolves or is associated with:

• Related to [Feature]: Better Tado X support #117

---

Type of Changes

Mark the type of changes included in this pull request:

• Bugfix
• New Feature
• Documentation Update
• Refactor
• Other (please specify):

---

Checklist

• I have tested the changes locally and they work as expected.
• I have added/updated necessary documentation (if applicable).
• I have followed the code style and guidelines of the project.
• I have searched for and linked any related issues.

[Moritz-Schmidt]

I think about doing something similar for the Zone classes and have some more Ideas for improvement, I think those Ideas should be discussed first before I put a lot of work in them. I'll open a new discussion for that.

[wmalgadey]

@erwindouna I like this change, should we merge it bevor your changes to my_tado.py? It will introduce some merge conflicts in #127 and #124

[erwindouna]

Great work here, @Moritz-Schmidt!
@wmalgadey a rebase needs to take place anyhow. Just need to decide where it will hit. I think it make sense to finish the earlier PR's and then try to rebase this PR.