feat(jsonrpc): use regex named group for path-tenant routing

[ehsavoie]

• Replace fixed POST / route with wildcard regex carrying (?...) so multi-segment paths (e.g. /org/team) are captured without string manipulation
• Validate consistency: URL tenant ≠ body tenant → InvalidParamsError
• Add @priority(1) to test helper routes so Vert.x evaluates them before the A2AServerRoutes catch-all (priority 20)

Fixes #1034 🦕

[omatheusmesmo]

Hi @ehsavoie , thanks.

Ran the paths from the issue against this branch and against main, same probes both times.

Request	main	this PR
POST /tenant1/	405	tenant "tenant1"
GET /.well-known/agent-card.json	200	200
GET /some-unmatched-path	404	405
DELETE /some-unmatched-path	404	405

Behaves as expected. Path tenant, multi-segment, trailing slash and the body/URL mismatch validation all work.

One thing worth a look: the catch-all ^/(?<tenant>.*)$ matches every path and is POST only, so any non-POST request to any unmatched path now returns 405 where it returned 404. That reaches applications sharing the HTTP port, not just A2A paths.

[ehsavoie]

One thing worth a look: the catch-all ^/(?.*)$ matches every path and is POST only, so any non-POST request to any unmatched path now returns 405 where it returned 404. That reaches applications sharing the HTTP port, not just A2A paths.

@omatheusmesmo Yes but we can't just filter on the tenant. You application would have to have something after the second / Maybe we could make that multitenancy configurable so that the catch all route would only be activated by setting a configuration property? WDYT ?

[ehsavoie]

@omatheusmesmo would the changes I've added in the right direction ?