The behave test files in the image sources are disorganised. They're structure reflects their history, but not the current image source layout. It's not clear where certain new tests should live, etiher in an existing file or a new one; it's inconsistent with respect to what tests run on what images, and it's not easy to see what kind of test coverage we have for the image source (particularly the modules).

I propose we re-organise the tests to a heirarchical structure that matches the modules. For example we have

modules/proxy
modules/run
modules/jdk/17
modules/maven 

So I think we should have

tests/features/proxy
tests/features/run
tests/features/jdk/17
tests/features/maven 

etc., OR, consider co-locating tests in the module file-path. According to https://docs.cekit.io/en/latest/handbook/testing/behave.html?highlight=behave#test-file-locations , we could now have e.g.

modules/proxy/tests/features/proxy.feature

It would be quickly apparent whether a module had any test coverage or not based on the structure.

Modules that are only used by the builder images would have corresponding tests that only run on the builder images; same for the runtime images.

This change should be a no-op from the container source POV, so it should not impact container binary content. It might result in a change to which tests run against each image.