Utilize test data from aas-core3.0-testgen rather than our proprietary set. #109

Issue:
We've been using our proprietary test set for validating the SDK against the metamodel. However, with every change in the metamodel that necessitates an update to our SDK, we find ourselves having to make corresponding adjustments to our test data. This iterative process is resource-intensive and can lead to potential inconsistencies and oversights.

Proposal:
To streamline this process and ensure a more robust testing framework, we recommend transitioning to the test data provided by aas-core3.0-testgen. Here are the key benefits of making this switch:

1. Comprehensive Coverage: The aas-core3.0-testgen provides an extensive set of test data, ensuring thorough validation of our SDK against a wide range of scenarios.

2. Automatic Generation: The test data from aas-core3.0-testgen is automatically generated, which means we'll always have the most up-to-date test cases without the manual effort of creating or updating them.

3. Reduced Maintenance: By relying on this external test set, we can significantly reduce the overhead associated with maintaining our own test data. This will allow our team to focus on enhancing the SDK and addressing other critical priorities.

4. Consistency with the Community: Adopting a widely-used test set ensures that our SDK is in alignment with community standards and best practices.

Next Steps:
We should initiate a transition plan to integrate aas-core3.0-testgen test data into our testing pipeline. This will involve:

• Setting up a mechanism to regularly fetch the latest test data from aas-core3.0-testgen.
• Adapting our testing infrastructure to utilize this new data source.
• Conducting an initial comprehensive test run to identify any gaps or inconsistencies.
• Decommissioning our proprietary test set once the transition is complete and verified.