Separate Constraint Verification from Setting of Attributes

[s-heppner]

Currently, we check constraints of attributes when they are set.
While this way, we never allow for non-compliant data, there are some instances where a temporary non-compliance is helpful, such as when copying and pasting an object.
Therefore, we should think about implementing a more modular pattern, separating the verification of the constraints from the actual setting of attributes and make it into a function that can be called when needed (for example when serializing).
This could be oriented at the implementation of the aas-core3.0-python verification.py.