Add provisioned vGpus in VM's devices list. (backport #1154)

[mergify]

Summary

It adds the vGpu devices tracked in VM's annotation to the VM's vGpu list.
Those vGpus are provisioned by Harvester when creating new clusters from Rancher.

PR Checklist

• Is this a multi-tenancy feature/bug?
  • Yes, the relevant RBAC changes are at:
• Do we need to backport changes to the old Rancher UI, such as RKE1?
  • Yes, the relevant PR is at:
• Are backend engineers aware of UI changes?
  • Yes, the backend owner is:

Related Harvester Issue harvester/harvester#6638
Blocks rancher#11399

Occurred changes and/or fixed issues

Technical notes summary

• We need to define how to remove the provisioned vGpus. cc @ibrokethecloud

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

---

This is an automatic backport of pull request #1154 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of ca6ff46 has failed:

On branch mergify/bp/release-harvester-v1.3/pr-1154
Your branch is up to date with 'origin/release-harvester-v1.3'.

You are currently cherry-picking commit ca6ff4699.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   pkg/harvester/config/labels-annotations.js
	both modified:   pkg/harvester/edit/kubevirt.io.virtualmachine/VirtualMachineVGpuDevices/index.vue
	both modified:   pkg/harvester/models/kubevirt.io.virtualmachine.js

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[a110605]

LGTM