Determine default startlevel configuration

[splatch]

OH3 release introduced startlevel concept and related service which coordinate activation of certain functionalities.

Core services such as persistence, rules and so got chained into phases which can be arranged via configuration file. In order to active next phase all services for earlier one must be published.

From my initial test it seems that we need following:

# Add dsl:persist,dsl:items,dsl:things when using text files
20=managed:item,managed:thing,managed:itemchannellink
30=persistence:restore
# below are related to rules
#40=dsl:rules,managed:rule,rules:refresh,rules:dslprovider
#50=ruleengine:start
#70=dsl:sitemap ?
80=things:handler

I performed test using custom build hence my config requirements were rather small compared to typical OH deployment. Given that our distro does not install thing-model, item-model, persistence-model and associated runtime/ide bundles we not require at least some of above.

[cdjackson]

I wonder if it might be good to make this a filtered resource so we can specify the start config as a property in the assembly pom? It might make it more configurable, and given we have a more "configurable" system than OH, it might make sense?