The bo4e-python from bo4e

Implement BusinessObject "Marktlokation" and add a unittested method to validate the MarktlokationsId

Hey Kevin,
as you might already know the so called "Marktlokation" is a central part of the German energy market. This is why it is also an important business object ("BO") in BO4E. Could you please implement the BO according to the official documentation?

Please also add a unittested method to validate the marktlokationsId similar to this method in our DotNet implementation and the respective unittests

implement mandatory properties ( in _MarktlokationBase)
implement optional properties, defaulting to None (in _MarktlokationDefaultBase)
add a method to validate the marktlokationsId (I'd suggest to make it static to be used without a surrounding malo object)
write a unittest for the validation method

Please create a new feature branch, branching off from develop and create a PR once ready.

Implement ENUM Waehrungscode

https://www.bo4e.de/dokumentation/enumerations/enum-wahrungscode
bitte nicht aus der tabelle rauskopieren, die ist broken.
Besser etwas, das schon code ist: https://github.com/Hochfrequenz/go-bo4e/blob/main/enum/waehrungscode/waehrungscode.go

Implement ENUM Messpreistyp

https://www.bo4e.de/dokumentation/enumerations/enum-messpreistyp

Translate all Docstrings to German

English should only be a secondary option.

Implement ENUM Bilanzierungsmethode

https://www.bo4e.de/dokumentation/enumerations/enum-bilanzierungsmethode

Fix user warnings in setup.cfg

C:\workspaces_test\BO4E-python\.tox\coverage\lib\site-packages\setuptools\dist.py:691: UserWarning: Usage of dash-separated 'project-urls' will not be supported in future versions. Please use the underscore name 'project_urls' instead
  warnings.warn(
C:\workspaces_test\BO4E-python\.tox\coverage\lib\site-packages\setuptools\dist.py:691: UserWarning: Usage of dash-separated 'author-email' will not be supported in future versions. Please use the underscore name 'author_email' instead
  warnings.warn(
C:\workspaces_test\BO4E-python\.tox\coverage\lib\site-packages\setuptools\dist.py:691: UserWarning: Usage of dash-separated 'long-description' will not be supported in future versions. Please use the underscore name 'long_description' instead    
  warnings.warn(
C:\workspaces_test\BO4E-python\.tox\coverage\lib\site-packages\setuptools\dist.py:691: UserWarning: Usage of dash-separated 'long-description-content-type' will not be supported in future versions. Please use the underscore name 'long_description_content_type' instead
  warnings.warn(
C:\Python38\lib\distutils\dist.py:274: UserWarning: Unknown distribution option: 'use_scm_version'
  warnings.warn(msg)

Change repo settings to have only default/main branch

Hi, since releases will be built by tagging commits on main and merges to main are not squashed: Is there still a need for the develop branch or could we maybe omit the develop->main merges?

Improve Enum construction

At the moment the enums are generated during runtime. This is now fine cause it works, but your IDE of choice is not able to make suggestions in this way.
It should be like the HTTPStatus enum

from http import HTTPStatus

HTTPStatus.ACCEPTED

The main struggle is the string representation for the serialization. But this issue should be solveable.

class EinNeuesEnum(StrEnum)
    """
    EinNeuesEnum ist ein Muster-ENUM
    """
    PYTHON_WERT = "SERIALISIERTER WERT (z.B. in JSON)" #: docstring für python wert

see f.e. #81