Execution Environment inheritance

[sivel]

Summary

It just recently ocurred to me that if a user is using another EE as the base image, they still require specific knowledge about how that other EE was built to properly interact and build off of it.

An example would be something like:

dependencies:
  python_interpreter:
    package_system: python3.11
    python_path: /usr/bin/python3.11
[...]
options:
  package_manager_path: /usr/bin/microdnf

There may be other configurations I have no thought of that could also benefit from the above.

This FR is basically an idea that would could store that type of info somehow in or on the image in a way that if not provided by the layered EE definition, that it could use the configuration of the base image if it exists.

[Zokormazo]

the init_container stuff would be interesting too.

And if we go further, knowing the packages/collections that are already installed would be great to not try to install them :)