ACA-Py 1.0.1 update

[loneil]

Use aca-py 1.0.1 image, plugins repo tag update

Not updating references to OWF yet, upcoming in 1.1.0

Update Traction display version to 1.0.0, figure next release which includes ACA-Py 1.x.x update we'd want to update major version? Otherwise could do 0.6.0

[github-actions]

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

Deployment URLs ready for review.

[jamshale]

Ya. have a major version is usually when it's mature and in production which traction certainly is.

[esune]

👍🏻

Regarding the TenantUI versioning scheme: we could follow the numbering ACA-Py uses in general (that is, also in the innkeeper plugin which we never update version-wise). I am however wondering if we should just version things independently since no real big change has been pushed to the application itself...

[loneil]

We may do multiple Traction releases on a single ACA-Py version though. But yeah the "Tenant UI version" is really just something to have in the package JSONs and I always just match it to what the release tag for Traction is.

Technically I guess someone could out-of-sync the 2 and have Traction on release 1.4.2 and the Tenant UI still on 1.1.1 or something (might have some things not work properly though) so the individual version number would at least tell them about the version syncing