Update skewer version to v0.0.19 (master)

[rakechill]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Updates a dependency version: https://github.com/Azure/skewer/releases/tag/v0.0.19
Already done for 1.27-1.31 release branches. Will follow this up with updating on 1.32.

• 1.27: [Azure] Update vendor/module versions for 1.27 #7278
• 1.28: skipped, because it already had the correct version (link)
• 1.29: [Azure] Update vendor/module versions for 1.29 #7286
• 1.30: [Azure] Update vendor/module versions for 1.30 #7288
• 1.31: [Azure] Update vendor/module versions for 1.31 #7289

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @rakechill. Thanks for your PR.

I'm waiting for a kubernetes 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.

[tallaxes]

/lgtm
/approve

Already done for 1.27-1.31 release branches. Will follow this up with updating on 1.32.

@rakechill, please link to these PRs

[tallaxes]

/ok-to-test

[rakechill]

@tallaxes, @aleksandra-malinowska
I've updated this PR by:

1. reverting my original commit
2. running go get github.com/Azure/[email protected]. This properly updates skewer in go.mod + go.sum. The import statement is updated in azure_client.go due to it being incompatible with this newer version of skewer.

Previously, I ran go mod tidy which under the hood will update other dependencies, as well. This resulted in the dra dependency moving from indirect to direct.

I also have closed #7827 in favor of cherry-picking this into 1.32 via the bot.

[tallaxes]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: rakechill, tallaxes
Once this PR has been reviewed and has the lgtm label, please assign x13n 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:

• cluster-autoscaler/OWNERS

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

[tallaxes]

Previously, I ran go mod tidy which under the hood will update other dependencies, as well. This resulted in the dra dependency moving from indirect to direct.

This actually sounds correct, though maybe a bit surprising it is not up to date on master. Does this happen without skewer update as well? If Yes, then please submit another PR with just go mod tidy update.