feat: (IAC-1108) Multi-tenancy process change - apply podtemplates before running onboard

[riragh]

Changes:

The new/improved DAC multi-tenant steps would be:

1. After the initial provider deployment has stabilized, run the onboard command
2. The onboard command would do following:
   • Copy all the required files and update all the required variables
   • Do the required steps for pod-templates and run SAS Software deploy steps to apply tenant pod-templates
   • Wait for ~7 mins
   • Apply the tenant onboard step and run sas-tenant-onboard job
   • Wait for sas-tenant-onboard job to reach running state.
   • Wait for 2 more mins for sas-tenant-onboard job to trigger the mid-tier services restart
3. Continue with cas-onboard steps.

Tests:

Verified following scenarios, see internal ticket for details.

Scenario	Description	Order Cadence	Deploy method	Verification
1	Multi-tenancy enabled schemaPerTenant deployment	Fast 2020	ansible, DO: false	Viya4 deployment stabilized and was accessible. Pod templates for each tenant created before onboard
2	Multi-tenancy enabled databasePerTenant deployment	Fast 2020	ansible, DO: true	Viya4 deployment stabilized and was accessible. Pod templates for each tenant created before onboard
3	Multi-tenancy enabled databasePerTenant deployment, different SASprovider passwords for tenants	Fast 2020	ansible, DO: true	Viya4 deployment stabilized and was accessible. Pod templates for each tenant created before onboard
4	Multi-tenancy enabled schemaPerTenant Risk products deployment	Fast 2020	ansible, DO: true	Deferred to CLT for verification