aasx.py: Add failsafe for writing and reading AASX files

[Frosty2500]

Previously, the failsafe parameter, allowing to skip errors and only log them as warnings instead, only existed for JSON and XML (de-)serialization.

This PR extends the feature to also be included when reading and writing AASX files.
For this, we add the failsafe boolean attribute to the AASXReader and AASXWriter classes in adapter.aasx.
If failsafe is True, the document is parsed in a failsafe way: Missing attributes and elements are logged instead of causing exceptions. Defect objects are skipped. The default value is False, keeping the existing behavior.

Furthermore, we do a little code-style clean up on string-formatting in the adapter.aasx module, updating all occurrences from (historically) different syntaxes to the more modern f-string syntax.

Fixes #228

[s-heppner]

Thank you! I see two things that still need some discussion:

• Do we really need the new class FailsafeConfigurable? It is a very shallow class with only one boolean parameter. I get that it standardizes the interface of how to interact with the failsafe configuration, but on the other hand, it adds additional complexity to each of the classes that inherit from it, for what could also be a simple attribute that "by chance" (our design) is the same across all of them.
• We could think about in some cases to return a logger.error instead of logger.warning, This still doesn't cause an exception, but for example when no AASX could be found, this could be seen as a more severe problem than just awarning.

Let's talk about this in our next meeting.

[Frosty2500]

I adapted one logger.warning to a logger.error but I am not sure about the rest. You can also gladly just write here what you think about them.
For the AASX I think it is ok to only give a warning when there are no AAS since one could have a process that automatically generates AASX and sometimes generates empty ones. Expect if we want to discourage this type of behaviour.

[s-heppner]

Can you go through the adapter.aasx one more time, adapting all the different string formatting syntaxes to only use "f-strings" (e.g. f"Submodel {submodel} could not be found or similar)?

When this was first written, f-strings did not exist yet and imo it's a bit messy that different syntax styles are used within one project, so this is a good opportunity to start cleaning this up, at least for aasx now.

[s-heppner]

LGTM. Thank you very much!