Tenant Issuer Config Fixes

[shaangill025]

Reopening #737 here as there were issues in the PR development environment after changing self_issuer_permission to auto_issuer in TenantRecord.

• resolve Configuration to create Tenants with default permission values #607
• resolve Block endorser connection and public DID tenant endpoints if Innkeeper approval is not set #608
• resolve Can't clear the connect_to_endorser and create_public_did fields in config #667

[github-actions]

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

Deployment URLs ready for review.

[esune]

I was able to create a tenant successfully. The profile page does not allow the tenant to connect to an endorser or publish a did since auto_issuer is set to false - that is good. I changed the value of auto_issuer to true in the argfile and restarted the container: on startup, aca-py still loads the auto issuer flag as False, even if the mounted config file is set to true.

[shaangill025]

I was able to create a tenant successfully. The profile page does not allow the tenant to connect to an endorser or publish a did since auto_issuer is set to false - that is good. I changed the value of auto_issuer to true in the argfile and restarted the container: on startup, aca-py still loads the auto issuer flag as False, even if the mounted config file is set to true.

Is this for traction_innkeeper, that is by design? New tenants created after setting auto_issuer to true should reflect that change in logs and tenant-ui [tested now locally using scripts].

[esune]

@shaangill025 you are right. The log statement relates to the innkeeper tenant, which only has admin role and will not connect to an endorser or publish a DID. I also apparently had restarted the wrong pod, after restarting the correct one and creating a new tenant everything works as expected.

[esune]

Tested new tenant creation as well as clearing existing settings, everything works as expected 👍🏻

[loneil]

👍 Did a quick test of this as well after getting back today by creating a new temp PR with the helm val set to true and all the Tenant UI/Innkeeper behaviour works as I'd expect. Created a new tenant in DEV as well after this was deployed (where the flag is false) and that is still working as expected too. Great stuff!

Probably need to decide if we'd want this flag set to true in pull request or "lower" envs by default in the helm vals as well.