fix(satp-hermes): correct add-counterparty-gateway operationId

[abhayrajjais01]

Summary

• Align AddCounterpartyGatewayEndpointV1.getOperationId() with the bundled OpenAPI entry for POST .../add-counterparty-gateway (AddCounterparty).
• getOperationId() previously read get-sessions-ids GET.operationId, which mislabels the route for authz, metrics, and generated clients.

Changes

File	Fix
packages/cactus-plugin-satp-hermes/src/main/typescript/api1/admin/add-counterparty-gateway-endpoint.ts	getOperationId() now resolves apiPath.post.operationId for /api/v1/@hyperledger/cactus-plugin-satp-hermes/add-counterparty-gateway, consistent with getPath() / getVerbLowerCase().

---

Pull Request Requirements

• Rebased onto upstream/main and squashed into single commit
• Signed-off-by present (DCO, human only)
• Conventional Commits format
• Assisted-by tag (if AI was used)

---

Character limit

• PR title and commit subject ≤ 80 characters
• Commit message body lines ≤ 102 characters

[Copilot]

Pull request overview

This PR fixes the SATP Hermes admin endpoint metadata so the add-counterparty route reports the correct OpenAPI operation ID.

Changes:

• Updates AddCounterpartyGatewayEndpointV1.getOperationId() to resolve AddCounterparty from the /add-counterparty-gateway POST operation.
• Aligns operation ID lookup with the endpoint’s existing path and HTTP verb metadata.

[RafaelAPB]

@abhayrajjais01 thank you! Running the tests, please remove the binaries from version control

[RafaelAPB]

@abhayrajjais01 please fix the failing pipelines and follow the new PULL.md and AI guidelines