🌱 (chore)[release-1.32]: Bump github.com/vmware/govmomi from 0.46.2 to 0.46.3 in /test/e2e

[dependabot]

Bumps github.com/vmware/govmomi from 0.46.2 to 0.46.3.

Release notes

Sourced from github.com/vmware/govmomi's releases.

v0.46.3

Release v0.46.3

Release Date: 2024-12-12

🐞 Fix

• [0ef1c709] toolbox: add freebsd stub for fileExtendedInfoFormat (#3620)
• [675534ae] vcsim: swap order of xsi type attribute (#2114)
• [1481d917] assert Entity interface in mo.Value()
• [3f5f8873] Property Collector updates should be triggered on the empty FilterSet (#3631)

💫 govc (CLI)

• [211be901] remove minimum API version check (#3643)

💫 vcsim (Simulator)

• [7bde166d] fix object.save when run directly against ESX
• [4aae3caf] LicenseManager enhancements
• [9ec310ac] add UpdateAssignedLicense method

🧹 Chore

• [e5dcb5f7] Update version.go for v0.46.3

⚠️ BREAKING

📖 Commits

• [e5dcb5f7] chore: Update version.go for v0.46.3
• [0ef1c709] fix: toolbox: add freebsd stub for fileExtendedInfoFormat (#3620)
• [7bde166d] vcsim: fix object.save when run directly against ESX
• [4aae3caf] vcsim: LicenseManager enhancements
• [675534ae] fix: vcsim: swap order of xsi type attribute (#2114)
• [211be901] govc: remove minimum API version check (#3643)
• [9ec310ac] vcsim: add UpdateAssignedLicense method
• [1481d917] fix: assert Entity interface in mo.Value()
• [3f5f8873] fix: Property Collector updates should be triggered on the empty FilterSet (#3631)

Commits

• e5dcb5f chore: Update version.go for v0.46.3
• 0ef1c70 fix: toolbox: add freebsd stub for fileExtendedInfoFormat
• 7bde166 vcsim: fix object.save when run directly against ESX
• 4aae3ca vcsim: LicenseManager enhancements
• 675534a fix: vcsim: swap order of xsi type attribute
• 211be90 govc: remove minimum API version check
• 9ec310a vcsim: add UpdateAssignedLicense method
• 1481d91 fix: assert Entity interface in mo.Value()
• 3f5f887 fix: Property Collector updates should be triggered on the empty FilterSet
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign lubronzhan 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 @dependabot[bot]. 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.