Remove or update globalMemoryLimit in devfiles' meta.yaml

[svor]

Is your task related to a problem? Please describe.

I don't see any reason to have globalMemoryLimit attribute in devfile's meta.yaml like this https://github.com/eclipse-che/che-devfile-registry/blob/master/devfiles/dotnet/meta.yaml#L6

Describe the solution you'd like

If this field isn't used, let's go through all devfiles and remove globalMemoryLimit from meta.yaml

Describe alternatives you've considered

If it used somewhere need to validate this value for each devfile.

[benoitf]

related to devfile/api#361

[nickboldt]

Sounds like this is related to the fix we did in redhat-developer/devspaces#455 to move memory limits from devfiles and into plugins.

For multi-arch support of Che on IBM Power, this is a must-have requirement, as ppc64le needs more ram than amd64 or s390x, so needs to be able to override defaults in the plugin registry and NOT have those overrides limited by devfiles setting lower limits.

[ericwill]

+1 to removing it, we have plenty of tools available when it comes to memory limits (plugin definitions, devfiles). I do not think we need a third one.

[l0rd]

Today we do not have a mechanism to tell the user that they should NOT try to run a Java stack on a 4GB or less Kubernetes node. That was a first step to try to setup that mechanism.

But as of today we are not using it and we are not maintaining that information. At this stage it's better to remove it.

[ericwill]

Fixed by eclipse-che/che-devfile-registry#379