refactor(EvseManager): more generic error checking

[a-w50]

• added utility function util::find_first_match, which behaves similar to std::visit:
  • it is given a matcher class as the first argument and a variadic amount of additional arguments, that possibly can have different types
  • the matcher class needs to overload its call operator for each of these types and implement a corresponding matching function
  • find_first_match will then execute the corresponding matching function for each argument in order and return the first value, which evaluates to true
• this utility function is used to write the check for active fatal errors within the EvseManager in a more generic fashion

Checklist before requesting a review

• I have performed a self-review of my code
• [] I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements

[SirVer]

looks good for BAZEL. Thanks!