Bump github.com/emicklei/go-restful from 2.9.6+incompatible to 2.16.0+incompatible

[dependabot]

Bumps github.com/emicklei/go-restful from 2.9.6+incompatible to 2.16.0+incompatible.

Changelog

Sourced from github.com/emicklei/go-restful's changelog.

Change history of go-restful

[v3.10.1] - 2022-11-19

• fix broken 3.10.0 by using path package for joining paths

[v3.10.0] - 2022-10-11 - BROKEN

• changed tokenizer to match std route match behavior; do not trimright the path (#511)
• Add MIME_ZIP (#512)
• Add MIME_ZIP and HEADER_ContentDisposition (#513)
• Changed how to get query parameter issue #510

[v3.9.0] - 2022-07-21

• add support for http.Handler implementations to work as FilterFunction, issue #504 (thanks to https://github.com/ggicci)

[v3.8.0] - 2022-06-06

• use exact matching of allowed domain entries, issue #489 (#493)
  • this changes fixes [security] Authorization Bypass Through User-Controlled Key by changing the behaviour of the AllowedDomains setting in the CORS filter. To support the previous behaviour, the CORS filter type now has a AllowedDomainFunc callback mechanism which is called when a simple domain match fails.
• add test and fix for POST without body and Content-type, issue #492 (#496)
• [Minor] Bad practice to have a mix of Receiver types. (#491)

[v3.7.2] - 2021-11-24

• restored FilterChain (#482 by SVilgelm)

[v3.7.1] - 2021-10-04

• fix problem with contentEncodingEnabled setting (#479)

[v3.7.0] - 2021-09-24

• feat(parameter): adds additional openapi mappings (#478)

[v3.6.0] - 2021-09-18

• add support for vendor extensions (#477 thx erraggy)

[v3.5.2] - 2021-07-14

• fix removing absent route from webservice (#472)

[v3.5.1] - 2021-04-12

... (truncated)

Commits

• ac666c0 update changes
• 9266625 use exact matching of allowed domain entries, issue #489 (#493) (#503)
• d9c71e1 support multipart/form-data (#502)
• 1e8c63c add access to Route from Request, issue #459 (#462)
• 0d68a53 fix typo (#465)
• a22b51d add check for wildcard (#463)
• 8dd9eb8 update chg
• e5d3175 add options shortcut (#455)
• 1f7f1de fix link to example
• 601692b examples use v3
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[kubevirt-bot]

@dependabot[bot]: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign omeryahud for approval by writing /assign @omeryahud in a comment. For more information see the Kubernetes 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

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a kubevirt 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/test-infra repository.

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten