chore(vm): memory limits on Pod for projects with quotas

[diafour]

Description

• Set proper memory limits when Project has quotas.

See also: deckhouse/3p-kubevirt#108

Why do we need it, and what problem does it solve?

Fix regression: kubevirt set increased memory limits after enabling memory hotplug in #2110.

What is the expected result?

Before:

VM:
spec.memory.size: 4096Mi

Pod:
    Labels:    resource-quota-overrides.deckhouse.io/discount-memory=361Mi
    ...					  
    Limits:
      memory:                                         9344909314    <- requests x2
    Requests:
      memory:                                         4672454657

4672454657 == 4456Mi
4096 + 361 = 4457

After:

VM:
spec.memory.size: 4096Mi

Pod:
    Labels:    resource-quota-overrides.deckhouse.io/discount-memory=361Mi
    ...					  
    Limits:
      memory:                                         4672454657    <- equal to requests, as intended
    Requests:
      memory:                                         4672454657

Checklist

• The code is covered by unit tests.
• e2e tests passed.
• Documentation updated according to the changes.
• Changes were tested in the Kubernetes cluster manually.

Changelog entries

[diafour]

/backport 1.8

[deckhouse-BOaTswain]

Failure: cherry-pick commit 6adacce to the branch release-1.8 failed. See Job for details.