Enhancements to Sentinel Workday Connector to Support Multiple Tenants

**Is your feature request related to a problem? Please describe.**
We have multiple Workday Tenants: Production, Sandbox, Sandbox Preview, and others. The current Data Connector only supports a single Tenant. I modified the Solution and re-imported it to allow us to have a separate Data Connector for each instance. However, Sentinel stops receiving logs from Sandbox when our Production Tenant is copied to Sandbox on a weekly basis. This results in a gap in log collection until we can Disconnect & Reconnect the Data Connector.

**Describe the solution you'd like**

1. Implement support for multiple Tenants
2. Allow for seamless/continued log collection through Tenant copies, which is common Workday practice. (I believe incorporating the use of refresh tokens would be a way to address this.)

**Describe alternatives you've considered**
N/A

**Additional context**
I think this occurs for the following reason: We give Sentinel an API Client ID and Secret so it can get an access token. This is the flow that's occurring:

- We connect Sentinel to Prod and it gets an access token (tokenA).
- We also connect Sentinel to SBX, which gets another token (tokenB).
- We're using the same API Client in both Prod and SBX so when it gets copied over, SBX is now expecting to see tokenA, which is what was in use in Prod. It fails b/c Sentinel is giving it tokenB.

This enhancement was previously submitted on 19May25 here: [Enhancements to Sentinel Workday Connector #12189](https://github.com/Azure/Azure-Sentinel/issues/12189). I'm resubmitting this as I was told "connector-related issues are now managed by a different team" so I'm hopeful this makes it to the right place now.