F entity role

Summary

Fixes unintuitive behavior of "Entity.role" after a retrieval.

(As per the bug report in the CaosDB matrix chat)

1. When an entity is retrieved with a class (i.e. a subtype of Entity) which does not match the entity role, an exception is being raised.
2. When an entity is retrieved using the Entity class, the correct role is set and available via Entity.role

Focus

The only real changes are in models.py. See the annotations for more info.

Everything else is just new tests covering the changes.

Test Environment

• No manual testing necessary.
• See unit tests in this MR
• See integration tests in caosdb-pyinttest!19 (merged)

Check List for the Author

• All automated tests pass
• Reference related Issues
• Up-to-date CHANGELOG.md
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there spezifications? Are they satisfied?
• remove xfail from pyint test (line 587; test_misc.py): @mark.xfail(reason="Waits for MR https://gitlab.indiscale.com/caosdb/src/caosdb-pylib/-/merge_requests/15")

For further good practices have a look at our review guidelines.

CHANGELOG.md

@@ -17,6 +17,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Fixed ###
 
+* Unintuitive behavior of `Entity.role` after a `Entity(id).retrieve()` where
+  the correct role is present now.
 * #53 Documentation of inheritance
 
 ### Security ###