[kata-containers] Update configuration-qemu to support kata containers 3.1.3.

[Alphadelta14]

What type of PR is this?
/kind bug

What this PR does / why we need it:

This updates configuration-qemu.toml to the latest 3.1.3 template.
Namely, the libexec paths have changed since 2.5.

This also makes kata_containers_virtio_fs_cache configurable.

Without this change, if you had upgraded from kubespray 1.22 (kata 2.4.1), you would have a dangling /opt/kata/libexec/kata-qemu/virtiofsd that doesn't interact properly with kata 3.1.3.
The newer /opt/kata/libexec/virtiofsd is the correct one.

For reference, the mismatched virtiofsd resulted in errors such as this:

Sep 21 00:11:38 ramiel virtiofsd[41676]: fuse: unknown option(s): `
Sep 21 00:11:38 ramiel virtiofsd[41676]: --cache=always
Sep 21 00:11:38 ramiel virtiofsd[41676]: --shared-dir=/run/kata-containers/shared/sandboxes/74e86dce5baadf07cdedba948df9faf722106913dbdf870022c1c0bd0246c42c/shared'
Sep 21 00:11:38 ramiel kata[41662]: time="2023-09-21T00:11:38.159340765Z" level=error msg="qemu-system-x86_64: -chardev socket,id=char-14283e4a190611ea,path=/run/vc/vm/74e86dce5baadf07cdedba948df9faf722106913dbdf870022c1c0bd0246c42c/vhost-fs.sock: Failed to connect to '/run/vc/vm/74e86dce5baadf07cdedba948df9faf722106913dbdf870022c1c0bd0246c42c/vhost-fs.sock': Connection refused" name=containerd-shim-v2 pid=41662 qemuPid=41677 sandbox=74e86dce5baadf07cdedba948df9faf722106913dbdf870022c1c0bd0246c42c source=virtcontainers/hypervisor subsystem=qemu

Special notes for your reviewer:
waiting on Corporate CLA to go through

Does this PR introduce a user-facing change?:

[kata-containers] Freshens configuration-qemu to latest template compatible with kata-containers 3.1.3.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Alphadelta14 / name: Heather Lapointe (44623b6)

[k8s-ci-robot]

Welcome @Alphadelta14!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @Alphadelta14. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[floryut]

@Alphadelta14 Thank you for the PR

Could you please check CLA ?

/ok-to-test

[Alphadelta14]

/check-cla

[mzaian]

Thanks @Alphadelta14

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Alphadelta14, floryut, mzaian

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:

• roles/container-engine/kata-containers/OWNERS [floryut,mzaian]

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