Define a mechanism for configuring what must be available in initial server start

The question of what content should be deployed into the runtime at the end of server start is somewhat distinct from what should be available overall. See JBAS-7713 for an example of how to make content available without requiring it to be deployed during server start.

The purpose of this JIRA is to define a configuration mechanism and API to make it easy for end users to specify what kind of on-demand behavior they want. The JBAS-7713 impl for M2 is using a simple boolean system property, but something that ties in with the overall behavior of the ProfileService is needed.

We need to make sure that profiles we ship that are configured out of the box to have expected behavior; e.g. a production profile would not have anything deploying on-demand; everything would be deployed as normal startup.