Upgrade K8s and Go versions

[WillardHu]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Update the versions of k8s and golang to keep consistent with the latest version of kubeedge.

Which issue(s) this PR fixes:

Fixes #

[kubeedge-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign moorezheng after the PR has been reviewed.
You can assign the PR to them by writing /assign @moorezheng in a comment when ready.

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

[WillardHu]

I split the changes into 5 commits for easier review.

• Upgrade K8s and Go versions - Modified go.mod and go.sum.
• Update go vendors - Automatically updated contents in the vendor directory after the update-vendor.sh script is executed.
• Update vendor licenses - Automatically updated contents in the LICENSES directory after the update-vendor-licenses.sh script is executed.
• Update client generation tools, remove k8s dependency, fix lint issues - Some file modifications caused by updating go and K8s versions (Need to focus on).
• Solved the vendor check to fail - Solved the problem that git does not recognize uppercase and lowercase letters in file names, causing vendor check to fail.

[tangming1996]

Could you also help change the version of the controller-gen tool in the Makefile to v0.15.0 to keep it consistent with Kubeedge?

[WillardHu]

Could you also help change the version of the controller-gen tool in the Makefile to v0.15.0 to keep it consistent with Kubeedge?

Done

[tangming1996]

Why was golint removed and revive introduced in the linters?

[WillardHu]

golint is no longer supported in golangci-lint

[tangming1996]

Was the following if logic removed because Sedna uses Go modules, thus eliminating the need for GOPATH?

if ! [[ "${GOPATH}/src/${SEDNA_GO_PACKAGE}/" -ef "${SEDNA_ROOT}/" ]]; then
    # Copy generated code into SEDNA_ROOT
    echo "Warning: ${SEDNA_ROOT} not included in $GOPATH which is required by code-gen"
    echo "Moving generated code from ${GOPATH}/src/${SEDNA_GO_PACKAGE}/pkg/ to ${SEDNA_ROOT}/"
    rsync -a ${GOPATH}/src/${SEDNA_GO_PACKAGE}/pkg/{client,apis} ${SEDNA_ROOT}/pkg
    if [ $? -eq 0 ]; then
        echo "Copy successful!"
        rm -rf ${GOPATH}/src/${SEDNA_GO_PACKAGE}/pkg/{client,apis}
    else
        echo "Error during copy of the generated code!" >&2
    fi
fi

[WillardHu]

The new versions of client-gen, lister-gen and informer-gen tools can specify the output directory through the --output-dir flag.

[tangming1996]

Thank you very much for your contribution. After the above issues are resolved, I'll give an "LGTM".

[tangming1996]

cc @MooreZheng

[tangming1996]

/lgtm