Zitadel upgrades

[srtalbot]

Summary

Upgrade to latest Zitadel stable version.

[patheard]

After the v2.62.0 upgrade, Zitadel was not able to read its configuration from the config.yaml file. This is likely a regression, so we upgraded to v2.61.1 and will wait for a fix.

[patheard]

Following the upgrade, we discovered several errors that were not directly related to the upgrade:

1. Service users were not being deleted from forms by the App. This meant that if a new service user was created for a form that had previously had one, a duplicate user exception was thrown. Addressed in (fix: Remove Service Account from Zitadel when API key is deleted. #3908)
2. The App's access token expiry was set to 60 minutes by the @zitadel/node dep, but Zitadel had this token expiry at 30 minutes, which was causing intermittent token expired errors. This has been fixed by setting the token timeout to 60 minutes in the Zitadel config. @bryan-robitaille is looking at creating our own interceptor for @zitadel/node so we can set whatever expiry time we want.
3. Several errors around being unable to set instance for requests were tracked down to clients closing their connection before Zitadel had a chance to respond. This type of context canceled error has now been suppressed to remove noise from the event channels.