Fixes/simplifications

[Alex Estevez (AEst2002)]

Description

• Removed -MinimumCommitmentDays and -ScheduleProfileStart parameters and associated logic from UpdateAzCapacityReservationCommand as updating an FCR is not supported for now.
• Removed error logic for -MinimumCommitmentDays and -ScheduleProfileStart in NewAzCapacityReservationCommand as these validations relied on values configured by CRP which are still subject to change. Instead, we want to rely on the service for any errors.
• Adjusted test logic to reflect the above
• Minor summary/description edits for accuracy/specificity.

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.)

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

• 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-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Aditya Pujara (a0x1ab)]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).