Upgrading TES deployment results in TES boot loop (failure to start)

[BMurri]

Describe the bug
Upgrading a TES deployment from before v5.3.0 results in a boot loop due to missing information in the configuration.

Steps to Reproduce
Steps to reproduce the behavior:

1. Deploy version of TES before v5.3.0
2. Upgrade with deployer for 5.3.0, 5.3.1, or 5.3.2.
3. Note stalling out and/or timeout failure of deployer.
4. Type Ctrl-C, then rerun deployer.
5. Note stalling out of deployer.
6. Check kubernetes container logs: TES image bootloops due to missing value for AzureCloudName.

Expected behavior
Upgrading deployment succeeds without stalling and TES service successfully initializes and runs.

Additional context
This does not repo when using the CoA deployer.