[Automation] Fixed time zone issue while creating an update deployment schedule

[dmohanta]

New-AzAutomationSoftwareUpdateConfiguration cmdlet is creating schedule by taking the UTC value as the StartTime instead of local time.

Description

New-AzAutomationSoftwareUpdateConfiguration cmdlet is creating schedule by taking the UTC value as the StartTime instead of local time.
When passing the start time and expiry time to the api, its converted to UTC, which the api assumes to be in local time and creates the suc accordingly.
Removing ToUniversalTime() in start time and expirty time while creating the suc object.

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
    • {Please put the link here}
  • the markdown help files have been regenerated using the commands listed here

[BethanyZhou]

Hi @dmohanta , please update changelod.md to describe the change you made in this pr.

[BethanyZhou]

Hi @aessing and @dmohanta , changelog.md should be updated before we merge this pr. It's required according to our development guideline: https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/azure-powershell-developer-guide.md#change-log

[dmohanta]

Hi @dmohanta , please update changelod.md to describe the change you made in this pr.

Done.

[dmohanta]

Hi @dmohanta , please update changelod.md to describe the change you made in this pr.

Done