implement split SV deployment migration procedure

[mblaze-da]

cluster test - to prove that current scratchnet deployment, without any config changes, still works

In addition I tested the migration on a scratchnet manually. The steps go as follows:

1. make sure that the current IaC gets applied at least once since it introduces new outputs required in the next step
2. set synchronizerMigration.migrateToSplitSvDeployment to true and let all stacks update
3. pause operator for sv stacks (needed to avoid conflicts in step 4.)
4. remove synchronizerMigration.migrateToSplitSvDeployment and set synchronizerMigration.splitSvDeploymentEnabled to true
5. unpause operator for sv stacks and let it apply

Next steps, after merging:

• test on scratche with big query enabled and change default scratchnet config to split SV
• migrate CILR

[canton-network-da]

[backport] Reminder

Please consider backporting to the following branches:

• release-line-0.7.0
• release-line-0.6.14
• release-line-0.6.13
• release-line-0.6.12

▶️ Please check the boxes for branches that you wish to backport to and backport PRs will
automatically be created when you merge this PR.

And your PR is currently against base branch: main.

Note: Any PR comment containing [backport] will be considered for auto-backporting upon merge,
you can always add those manually for PRs that did not get these reminders. You can also edit
this comment manually and add more branches that this should be backported to.

[mblaze-da]

/cluster_test

[github-actions]

Deploy cluster test triggered for Commit 2bbc0dff5aa71d0f0afc519ad0a93c3a6c1401d4 in , please contact a Contributor to approve it in CircleCI: https://app.circleci.com/pipelines/github/DACH-NY/canton-network-internal/76927