chore: fix implictly required vendor

[nilo19]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

/kind failing-test

What this PR does / why we need it:

go get github.com/fsnotify/fsnotify@v1.4.9
go mod tidy
go mod vendor

Related: #774 (comment)

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Release note:

chore: fix implictly required vendor

[coveralls]

Coverage remained the same at 80.584% when pulling 9fc7a48 on nilo19:fix/vendor into 9869e9d on kubernetes-sigs:master.

[nilo19]

/test pull-cloud-provider-azure-check

[andyzhangx]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx, nilo19

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andyzhangx,nilo19]

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

[MartinForReal]

/cherrypick release-1.1

[MartinForReal]

/cherrypick release-1.0

[k8s-infra-cherrypick-robot]

@MartinForReal: #775 failed to apply on top of branch "release-1.1":

Applying: chore: fix implictly required vendor
Using index info to reconstruct a base tree...
M	go.mod
M	pkg/azureclients/armclient/azure_armclient_test.go
M	pkg/azureclients/loadbalancerclient/interface.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging pkg/azureclients/loadbalancerclient/interface.go
Auto-merging pkg/azureclients/armclient/azure_armclient_test.go
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: fix implictly required vendor
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.1

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/test-infra repository.

[k8s-infra-cherrypick-robot]

@MartinForReal: #775 failed to apply on top of branch "release-1.0":

Applying: chore: fix implictly required vendor
Using index info to reconstruct a base tree...
M	go.mod
M	pkg/azureclients/armclient/azure_armclient_test.go
M	pkg/azureclients/loadbalancerclient/interface.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging pkg/azureclients/loadbalancerclient/interface.go
Auto-merging pkg/azureclients/armclient/azure_armclient_test.go
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 chore: fix implictly required vendor
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-1.0

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/test-infra repository.