Align TRQP flow with Ayra v2 endpoints

[nodlesh]

This PR aligns the CTS Trust Registry / TRQP flow with the current Ayra TRQP v2 API spec and removes stale confidence legacy endpoint behavior.

Key changes:

• Updates Registry/TRQP extension checks to use current Ayra endpoint paths.
• Keeps /authorization and /recognition as dedicated verification checks, not generic extension API checks.
• Updates TRQP suggestion helper paths.
• Replaces simulated TRQP tester success with real endpoint-based results.
• Prevents Full conformance when real upstream checks fail.
• Adds focused regression tests for endpoint paths, request bodies, response handling, suggestions, and TRQP tester behavior.
• Adds ACA-Py demo/test runbook for the internal issuer/holder/verifier setup.
• Fixes related demo-flow issues found during manual testing:
• Issuer report no longer shows success when issuance failed.
• ACA-Py issuer and holder controllers are kept separate.
• ACA-Py connection wait avoids returning stale non-active records.
• Docker dev container gets an isolated conformance-stack/node_modules volume.

Notes:
Holder and Verifier TRQP enforcement behavior was not intentionally changed.
did:webvh strict mode and TRQP response signing/JWS are intentionally out of scope.

Verification:

docker compose --profile with-ngrok up --build app acapy-control acapy-holder-control acapy-verifier-control ngrok

Run the TRQP Flow

Use the following data to verify the TRQP flow

did:web:sandbox.ayra.network

Authorization:
Entity ID:    did:web:ayra-cts-issuer.ngrok.app:issuer
Authority ID: did:web:sandbox.ayra.network
Action:       issue
Resource:     ayracard:businesscard
Context:      {}

Recognition:
Entity ID:    did:web:sandbox.ayra.network
Authority ID: did:webvh:ayra.forum
Action:       member-of
Resource:     ayratrustnetwork

closes #31