Add GOPACSHandler day-ahead UFTP flow tests

[Miggets7]

Summary

Adds test coverage for the GOPACSHandler day-ahead capacity-steering message flow on the AGR (EMS) side, closing the gap left by the UFTP V2→V3 participant migration (#40). The ems module previously had no tests for the GOPACS handler.

The spec drives real signed UFTP messages through the handler's actual entry point (processRawMessage) using libsodium crypto — no database, no container, no network. Inbound payloads are embedded as XML fixtures matching the real wire format (DSO nilsgrid.net → AGR openremote.io, v3.0.0, attribute-style). A small test-support constructor on GOPACSHandler skips remote config (OAuth client / private-key file) and JAX-RS deployment; a RecordingGOPACSHandler subclass captures outbound messages (both the library-generated responses and the handler-built FlexOffer); scheduled work runs inline for deterministic assertions.

Covered flows:

• FlexRequest → asset updated from request ISPs (powerMaximumFlexRequest = importMax, powerMinimumFlexRequest = exportMax); replies with FlexRequestResponse (Accepted) then FlexOffer. The emitted FlexRequestResponse is asserted to match the reference message shape (result, referenced request id, swapped domains, version, conversation id).
• FlexOfferResponse (Accepted and Rejected) → handled with no asset mutation and no reply.
• FlexOrder → asset updated from order ISPs (currentPowerFlexRequest, plus the offtake powerLimitMaximumProfileFlexOrder / feed-in powerLimitMinimumProfileFlexOrder profile); replies with FlexOrderResponse (Accepted).
• Out-of-scope drop → a validly-signed FlexRequest whose CongestionPoint differs from the contracted EAN is dropped: no asset mutation, no reply (the V3 re-scoping).

[Copilot]

Pull request overview

Adds isolated Spock-based test coverage for the GOPACS UFTP day-ahead message flow on the EMS/AGR side by driving real signed UFTP v3.0.0 XML payloads through GOPACSHandler.processRawMessage, and introduces a test-support constructor to wire collaborators without container/OAuth/JAX-RS setup.

Changes:

• Add GOPACSHandlerTest covering FlexRequest → (FlexRequestResponse + FlexOffer), FlexOfferResponse handling, FlexOrder flows, and out-of-scope congestion point dropping.
• Add a protected test-support constructor on GOPACSHandler to allow exercising message handling without container wiring and remote configuration.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
ems/src/test/groovy/org/openremote/extension/ems/manager/gopacs/GOPACSHandlerTest.groovy	New Spock spec with signed-message fixtures and assertions for day-ahead GOPACS/UFTP flows.
ems/src/main/java/org/openremote/extension/ems/manager/gopacs/GOPACSHandler.java	Adds a test-support constructor to instantiate the handler with injected services/executor/private key and without deployment/remote config.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Miggets7]

This path already degrades gracefully — no NPE is thrown.

1. fetchBearerToken() wraps the gopacsAuthResource call in try/catch (Exception e). A null gopacsAuthResource raises an NPE, which is caught and the method returns "".

2. getParticipantInformation() checks the blank token before touching the address book:

String authorization = fetchBearerToken();
if (authorization.isBlank()) {
    LOG.warning("Skipping participant lookup for " + domain + ": no OAuth2 bearer token available");
    return Optional.empty();
}
try (Response response = gopacsAddressBookResource.fetchParticipantByDomain(authorization, domain)) {

So even with participants unseeded: caught NPE → blank token → Optional.empty(), and gopacsAddressBookResource is never dereferenced. Additionally, the covered flows pre-seed participants, so the participants.containsKey(domain) cache returns first and fetchBearerToken() is not called at all.

Leaving the constructor as-is; no-op resource implementations would be unused plumbing.