Bump up the version of EVerest to the latest release

[shankari]

• Bump up the version of EVerest to the latest one 2024.2.0
• Bump up our own tag (to 0.0.12)
• Change the preconfigured DB to match the new format - This involved copying out the unmodified DB and changing the connection URL as before (update VARIABLE_ATTRIBUTE set "VALUE" = '[{"configurationSlot": 1, "connectionData": {"messageTimeout": 30, "ocppCsmsUrl": "ws://host.docker.internal/ws/cp001", "ocppInterface": "Wired0", "ocppTransport": "JSON", "ocppVersion": "OCPP20", "securityProfile": 1}}]' where VARIABLE_ID == 161;)

The station is able to connect successfully

2024-03-11 04:26:37.025275 [INFO] ocpp:OCPP201     :: OCPP client successfully connected to plain websocket server
2024-03-11 04:26:37.034272 [INFO] ocpp:OCPP201     :: Received BootNotificationResponse: {
    "currentTime": "2024-03-11T04:26:37.000Z",
    "interval": 300,
    "status": "Accepted"
}
with messageId: 170dc257-4035-4fcd-868a-32da294db0ba

Although there are several weird errors related to the lack of errors :)

2024-03-11 04:26:37.056587 [ERRO] manager         void Everest::error::ErrorCommBridge::handle_request_clear_error(const json&) :: Error while clearing errors: No errors matched the request.
2024-03-11 04:26:37.065594 [INFO] evse_manager_2:  :: All errors cleared

And some non-transaction (informational) errors

2024-03-11 04:30:00.077355 [ERRO] ocpp:OCPP201    ocpp::EnhancedMessage<M> ocpp::MessageQueue<M>::receive(const std::string&) [with M = ocpp::v201::MessageType; std::string = std::__cxx11::basic_string<char>] :: Received a CALLERROR for message with UID: 4851748d-6271-40dc-89d9-13a4c740e39f
2024-03-11 04:30:00.077503 [WARN] ocpp:OCPP201    void ocpp::MessageQueue<M>::handle_timeout_or_callerror(const std::optional<ocpp::EnhancedMessage<M> >&) [with M = ocpp::v201::MessageType] :: CALLERROR for: MeterValues (4851748d-6271-40dc-89d9-13a4c740e39f)
2024-03-11 04:30:00.077558 [WARN] ocpp:OCPP201    void ocpp::MessageQueue<M>::handle_timeout_or_callerror(const std::optional<ocpp::EnhancedMessage<M> >&) [with M = ocpp::v201::MessageType] :: Message is not transaction related, dropping it

I also don't see the enhanced error codes in the UI, but maybe we have to use a different nodered config to see it...