fix: Enable networkInterfaceMultiqueue only if sockets > 1

[0xFelix]

What this PR does / why we need it:

Enable networkInterfaceMultiqueue only if the amount of sockets is greater than one, since networkInterfaceMultiqueue requires at least two sockets.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

networkInterfaceMultiqueue is only enabled if the template has more than one socket

[ksimon1]

/lgtm
/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ksimon1

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:

• OWNERS [ksimon1]

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

[0xFelix]

/test e2e-gcp-common-templates-centos6

[kubevirt-bot]

@0xFelix: No presubmit jobs available for kubevirt/common-templates@master

In response to this:

/test e2e-gcp-common-templates-centos6

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.

[0xFelix]

/retest-required
/cherry-pick release-v0.29

[kubevirt-bot]

@0xFelix: once the present PR merges, I will cherry-pick it on top of release-v0.29 in a new PR and assign it to you.

In response to this:

/retest-required
/cherry-pick release-v0.29

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.

[kubevirt-bot]

@0xFelix: new pull request created: #587

In response to this:

/retest-required
/cherry-pick release-v0.29

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.