[Az.Migrate] Stabilize command internals & update policy defaults

[minhsuanlee]

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

  • [x] General release
  • [ ] Public preview
  • [ ] Private preview
  • [ ] Engineering build
  • [ ] No need for a release

• [x] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • Update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd[bot]]

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

[isra-fel]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).

[minhsuanlee]

Replication policy now aligns with Portal UX for default config.

Passing dev test with private module 3.0.17: https://dev.azure.com/msazure/One/_build/results?buildId=143763316&view=results

[notyashhh]

Hey @minhsuanlee, @mayada83,

1. What are these changes related to?
2. Why did you remove all the test cases?

[notyashhh]

@minhsuanlee, @mayada83, Is this PR still targeting 15.1?

[minhsuanlee]

Hey @minhsuanlee, @mayada83,

1. What are these changes related to?
2. Why did you remove all the test cases?

1. What are these changes related to? a. Putting back usage of $PSBoundParameters in AzLocal commands b. Update Policy default values to align with the product

2. Why did you remove all the test cases? Following the suggestion by Joyer Jin from PS team, I've created a more comprehensive unit test of Test-AzMigrateLocalEndToEnd.Recording.json to test the entire scenario of AzLocal migrate instead of testing individual commands separately