Add MREC9AuthorizationTimeout Error

[corneliusclaussen]

Describe your changes

Add support for MREC9 authorization timeout error code reporting (car was plugged but never authorized)

Issue ticket number and link

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

[Pietfried]

This currently causes some issues with OCPP1.6 since the error raising and SessionEvents do overlap in a way here, potentially causing something like:

Is it intended that this error prevents charging (also causing yet another StatusNotification.req in OCPP)?

[corneliusclaussen]

Is it intended that this error prevents charging (also causing yet another StatusNotification.req in OCPP)?

This is debatable. In principle yes, as no charging shall be possible without replugging. I'm not sure if the Auth manager already takes care of this, in which case we would not need a second inoperative here. ChargeX is unfortunately absolutely unclear on how they thought this should be used.

[Pietfried]

Is it intended that this error prevents charging (also causing yet another StatusNotification.req in OCPP)?

This is debatable. In principle yes, as no charging shall be possible without replugging. I'm not sure if the Auth manager already takes care of this, in which case we would not need a second inoperative here. ChargeX is unfortunately absolutely unclear on how they thought this should be used.

Ok. The EvseManager already publishes a PluginTimeout session event so the information is already transmitted (StatusNotification(status=Finishing, info=ConnectionTimeout) without the MREC error. I still think its ok to send another informational StatusNotification for it