Support pydantic code generation

[chicco785]

Description

Support pydantic code generation

Changes Made

• generate a new langpack for pydantic
• support EQ and GL profiles
• support enums correctly
• leverage python native data types (without need of duplicating them e.g. Boolean for bool)
• support geo dataypes for easier manipulation and query
• support cyclic references by stripping them to the first level during serialization
• Work around for potential issue in CIM schema: Multiplicity of PowerSystemResources attribute in Location is set to be M:1, but should be M:1..N

Related Issues

Fixes #3

Checklist

• I have used a PR title that is descriptive enough for a release note.
• I have tested these changes locally.
• I have added appropriate tests or updated existing tests.
• I have tested these changes on a dedicated VM or a customer VM [name of the VM]
• I have added appropriate documentation or updated existing documentation.

[chicco785]

testing the code generated revealed that:

• due to recursion of the model the approach of generating 1 file per class is not possible as a solution, pydantic validation will fail with several errors
• assigning default None to fields where the value is optional, causes recursion error. this implies though, we have to pass a value (None or [] for lists) when creating instances
• having too large pydantic schema, causes recursion error, so the version of the code generates only EQ classes

[chicco785]

There may be some bugs in the CIM schema, in particular:

• Multiplicity of PowerSystemResources attribute in Location is set to be M:1, but should be M:1..N.

[chicco785]

to test:

• alternative ways to set default values (see RecursionError: maximum recursion depth exceeded pydantic/pydantic#6993)
• split classes based on profile

[chicco785]

to test:

• alternative ways to set default values (see RecursionError: maximum recursion depth exceeded pydantic/pydantic#6993)
• split classes based on profile

this eventually will be handled in a separate pr corresponding issues will be opened.

[chicco785]

@MarcoPignati also alliander is working on something similar with a slight different approach, it's worth having a chat with them: sogno-platform#18