Error framework is not thread safe

[corneliusclaussen]

Describe the bug

The error framework is currently not thread safe. If multiple threads are raising/clearing errors invalid states within the error database of a module can happen, e.g. raising the same error twice or trying to clear an error that is no longer there. Some of those can trigger uncaught exceptions that exit the module.

EVerest Domain

Other

Affected EVerest Module

currently EvseManager, but possible any using the error framework in multiple threads

To Reproduce

In a real application, this can e.g. be triggered when using BSP and OVM as stable API modules and both raise a communication fault at the start up because the external API user process is missing.

As this happens at almost the same time it leads to the "Inoperative" error being set twice.

Anything else?

No response

[corneliusclaussen]

PR #1588 fixes the usage from multiple threads in EvseManager. It does not make the error framework thread safe, so potentially other modules may be affected as well. #1588 is still needed even if we make the error framework thread safe.