fix(Part B, Ch. 4.2) - Change the code in Adapter-Example

[Vasc01]

In addition to the changes I have made:

• As far as I understand the Adapter is for making old legacy code work with new code. In the examples the new code is adapted to the old. Perhaps a comment line over the classes with "Adaptee" and "Target" will help.

I found the two examples from the following link helpful: https://refactoring.guru/design-patterns/adapter/python/example#example-0

[braboj]

Yes, in the example we cover the typical use case where something new has to be adapted to something old. The adapter pattern works also in the opposite direction, but this is a rare scenario. Please revert the changes for applyConfig, because it demonstrates exactly a legacy interface written in Python 2.

⚠️ Please use issue numbers when committing. It is not a problem if there is a more generic issue, like 'Proofread Design Patterns' or something similar.

From PEP-8:

Function and Variable Names Function names should be lowercase, with words separated by underscores as necessary to improve readability. Variable names follow the same convention as function names. mixedCase is allowed only in contexts where that’s already the prevailing style (e.g. threading.py), to retain backwards compatibility.