Ensure Pillar handles OS memory reporting accurately

[OhmSpectator]

During tests, @cperakis discovered that EVE OS reports the memory allocated for a VM as still free when using the free tool. This behavior is also observed in /proc/meminfo. This could mean we should not trust what we get from the system as "free" memory. When Pillar requests free memory, it might include memory already allocated for an app, which could pose a problem when deciding on available resources for starting a new VM. This behavior is due to Linux's memory overcommitment, which does not mark the memory as non-free until it is really used.

Currently, as far as I remember we retrieve the "free memory" value by analyzing the MemAvailable line in /proc/meminfo:

eve/pkg/pillar/vendor/github.com/shirou/gopsutil/mem/mem_linux.go

Lines 92 to 98 in 078f891

	case "MemAvailable":
	t, err := strconv.ParseUint(value, 10, 64)
	if err != nil {
	return ret, retEx, err
	}
	memavail = true
	ret.Available = t * 1024

eve/pkg/pillar/hypervisor/hypervisor.go

Line 115 in 397dce6

hm.FreeMemoryMB = roundFromBytesToMbytes(vm.Available)

The task is to:

• Verify how this information is used later in Pillar.
• Ensure that Pillar correctly accounts for app-allocated memory, either by manual accounting in the code or by accurately interpreting the system-reported "free" memory.
• If it does not interpret it right - fix it.