Fixed scheduler time zone validation error

[louiseph]

The date time conversion was happening inside the form element causing confusing UI and potential validation errors when treating local time as UTC. Proposed solution would be to keep everything locale-based on the client side, while doing any UTC conversions on the backend by passing in the TimezoneOffset parameter.

[louiseph]

@microsoft-github-policy-service agree company="Microsoft"

[santhoshb-msft]

Hi @louiseph added some comments on this PR.

[louiseph]

 

Local Time: 12 pm PDT

	Expected behavior	Past Behavior	Actual Behavior
test < 5 am PDT	Doesn’t create metered trigger	Doesn’t create metered trigger	Doesn’t create metered trigger
5 am PDT < test < 12 pm PDT	Doesn't create metered trigger	Creates metered trigger	Doesn’t create metered trigger
12 pm PDT < test	Creates metered trigger	Creates metered trigger	Creates metered trigger

[santhoshb-msft]

@louiseph looks like its still showing the same issue. When I input the start time, it is not taking into account of the timezone and timezone is coming through as 0

[msalemcode]

Reviewed and tested the change and it worked as expected.

[santhoshb-msft]

@msalemcode I think lets hold off on this as when I tried with a different time zone browser it didnt work. Can you confirm if that works for you?

[santhoshb-msft]

Thanks @msalemcode and @code4clouds