Add other connection row advanced details

[loneil]

Lets make debugging some issues (and getting details about established connections) a lot quicker. Call additional connection details when digging into a Connection row.

• Endpoints
• Metadata

This stuff could be hidden with the developer flag if we'd prefer once there's production usage.

Should help with

• Mediator testing
• Endorser connection checking
• Other service endpoint issues

Examples:

---

---

---

---

[github-actions]

Deployment	Resource	Location
Traction
	Tenant UI	https://pr-829-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca
	Innkeeper UI	https://pr-829-traction-tenant-ui-dev.apps.silver.devops.gov.bc.ca/innkeeper
Aca-Py
	Admin Swagger	https://pr-829-traction-acapy-admin-dev.apps.silver.devops.gov.bc.ca/api/doc
	Tenant Proxy Swagger	https://pr-829-traction-tenant-proxy-dev.apps.silver.devops.gov.bc.ca/api/doc

Deployment URLs ready for review.

[jamshale]

I think more information is better as long as it doesn't cause to much confusion/clutter for end users. So I agree this make be too much in production.

Code looks good though 👍

[loneil]

Yeah I'm considering whether any of those expanders that show JSON all over the app should be developer flag hidden in production. So agree it's something to think about hiding in the not too far future.

[esune]

I like it! 👍🏻
Regarding hiding the functionality in production: I actually think it might be useful there more than anywhere to troubleshoot. Connections in particular is read/write in production as well to allow for OOB interactions, so this is great.