Bug with memory suggestions not making sense and being too big

[afbjorklund]

This is the greeting that new minikube users have seen in katacoda for years:

X The requested memory allocation of 2200MiB does not leave room for system overhead (total system memory: 2460MiB). You may face stability issues.
* Suggestion: Start minikube with less memory allocated: 'minikube start --memory=2200mb'

🧯  The requested memory allocation of 2200MiB does not leave room for system overhead (total system memory: 2436MiB). You may face stability issues.
💡  Suggestion: Start minikube with less memory allocated: 'minikube start --memory=2200mb'

The suggested "change" doesn't make any sense, from 2200 to 2200 (same) ? Especially not when being spelled as both "mebibyte" and "millibyte" at once.

And it also doesn't match the upstream recommendations, nor the code:

        minUsableMem            = 1800 // Kubernetes (kubeadm) will not start with less
        minRecommendedMem       = 1900 // Warn at no lower than existing configurations

The VM is already started with 2500M, which is well over the 2048M requirement: "2 GB or more of RAM per machine (any less will leave little room for your apps)."

It's fine to have 2200 as the default min memory, but the rest of it is just annoying spam.

        const fallback = 2200
        maximum := 6000

minikube version: v1.28.0 commit: 986b1ebd987211ed16f8cc10aed7d2c42fc8392f