Make Application subclasses available via our context during Feature executions

[spericas]

A global/shared Feature is executed for each Application subclass. This change makes the Application subclass available to the Feature during its execution. Just like for requests, the availability is through the Helidon context. Updated functional tests for multiple apps.

[tjquinno]

IIUC the developer's code (if it cares) needs to check which app the feature corresponds to. I see that the changes to the main (non-test) Helidon code now set the app subclass in the context but only the tests (i.e., the user code) retrieve it.

Or put another way, there is no other Helidon code that directly uses features and therefore might need to look at the app subclass?

[spericas]

IIUC the developer's code (if it cares) needs to check which app the feature corresponds to.

Yes, a Feature is executed for each app for which it is part of.

I see that the changes to the main (non-test) Helidon code now set the app subclass in the context but only the tests (i.e., the user code) retrieve it.

Yes, this is mostly for user's logic. We already make it available during execution (e.g. in a request filter) and also as part of the Helidon context.

Or put another way, there is no other Helidon code that directly uses features and therefore might need to look at the app subclass?

Right, I don't believe we use Features in Helidon (we use AutoDiscoverable from Jersey). This is mostly for app developers.