[Feature Request]: Validat the system Hop is running on

[mattcasters]

What would you like to happen?

I want to be able to specify requirments at the lifecycle environment level for the system on which Hop is executing pipelines and workflows.
We would want to have this before even attempting to execute anything, or even start a Hop server, Flight Server or py4j service.
Every time an environment is activated we want to check against the following:

• Validate that the JVM has enough memory or at least configured with the right -Xmx
• Validate that specific (local) folders have enough free disk space
• Validate that the system has a minimum number of CPU cores to work with

We want to have extra tab in the LifecycleEnvironmentDialog like we did in #7577 for the marketplace plugin environment check.

Issue Priority

Priority: 3

Issue Component

Component: Other