We included the regex pattern as-is from the input which caused problems
with the regex engines as the patterns in the meta-model are written in
a Python dialect (and assuming that the regex engine works on UTF-32
characters). However, most regex engines in the wild operating on SHACL
(*e.g.*, Java SHACL validators) use UTF-16 to represent the text and do
not support some parts of the Python regex dialect. For example, in
the input meta-model specification, we omit the minimum bound 0
(*e.g.*, ``{,4}``), which breaks with the Java regex engine beneath
the SHACL validator.

Instead, with this patch, we parse the pattern from the specification
and re-render it into the form that we also use in JSON Schema. We pick
JSON Schema regex dialect as most SHACL validators in the wild can deal
with it, in particular those based on Java as a platform. Hence, we
decide to serve this user base with priority.

Discovered in [aas-core-meta issue 342].
Fixed in [aas-core-codegen commit e22cc].

[aas-core-meta issue 342]: aas-core-works/aas-core-meta#342
[aas-core-codegen commit e22cc]: aas-core-works/aas-core-codegen@e22ccae

Previously we did not define `aas:environment`
directly via an `xs:element` tag, rather only
provided it directly as `xs:complexType`.
This created issues with several XML Schema
validator engines.

This commit fixes this problem,
discovered in #457.

Previously, the order of the attributes in class
`EmbeddedDataSpecification` got mixed up, making
the schemas of Release 3.0.8 not backward
compatible, as found out in #477.

This reverts the change of the order of attributes
back to the state of v3.0, so that the schemas are
properly backward compatible.

Fixes #477