feat(nodepool): support timezone for disruption budgets

[flavono123]

Fixes #1446, partially

Description

add the field disruption.budgets[].timeZone for NodePoolSpec.
if not set, use UTC as default.
validate if not schedule is set, timeZone also cannot be.

referenced one in CronJobSpec and already tried PR #1447

How was this change tested?

make verify && go test ./pkg/apis/v1/

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: flavono123
Once this PR has been reviewed and has the lgtm label, please assign gjtempleton for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @flavono123. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[flavono123]

are we have to emit a new event for a wrong timezone?:

If the time zone name becomes invalid during the lifetime of a CronJob or due to a change in host configuration, the controller will stop creating new new Jobs and will create a system event with the reason UnknownTimeZone

https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/cron-job-v1/#CronJobSpec

[coveralls]

Pull Request Test Coverage Report for Build 13538517552

Details

• 12 of 16 (75.0%) changed or added relevant lines in 2 files are covered.
• 3 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.04%) to 81.494%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
pkg/apis/v1/zz_generated.deepcopy.go	1	5	20.0%

Files with Coverage Reduction	New Missed Lines	%
pkg/controllers/provisioning/scheduling/nodeclaim.go	3	86.98%

Totals
Change from base Build 13509538416:	-0.04%
Covered Lines:	9283
Relevant Lines:	11391

---

💛 - Coveralls