Feat/validation of entities

[KristianKjerstad]

What does this pull request change?

• generate new dmss api, since the old code did not work with the entity validation endpoint.
• add validation of entities to import_package
• ther version of openapi generator has been updated, since there is a known bug in the old version that cased api calls to the validation endpoint to fail ([BUG] PYTHON Generated Client unable to parse response including array: [SCHEMA_OBJECT] OpenAPITools/openapi-generator#10564)

NB! a lot of files are changed, but the files inside the folder dmss_api can be ignored since they are autogenerated

NB! files inside tests/test_data/plugins_example are copied from dm-core-packages and should not require review

Issues related to this change

closes #103

[KristianKjerstad]

probably needs equinor/data-modelling-storage-service#470 for ci to pass

[KristianKjerstad]

test if validation works in dm cli if wrong type is saved in an attribute, for example text in boolean attr.

update: those issues are catched by the new validation

[KristianKjerstad]

validation in dmss is not working properly.

If trying to validate very nested objects (like the resolved root package), then the validation stops before reaching the "deepest" documents

Validation in dm-cli for the reset command is not trivial since we need ALL documents to be uploaded in ALL data sources before validation can start. This is because the order of uploading documents in dm-cli is not well defined. For example, dm-cli might upload all entities before all blueprints. Validation of entities cannot happen unless all blueprints the entity uses are already in dmss.

[KristianKjerstad]

replaced by #112