Add Tier level during adapter creation

[DutchmanNL]

Based on selection of adapter logic default tier level should be set accordingly to this definition:

Please add at least default tier 3, it would be nice to automatically adopt proper tier level based on adapter type selection

TIERS: Start instances in an ordered manner

Feature status: Technology preview (since 3.3.0)

Starting from js-controller 3.3.0, you can define the common.tier attribute in the io-package.json. Lower TIERS will start before higher TIERS. Currently, 3 TIER levels are supported. Note, that the admin adapter as the central control platform will always be started first.

TIER 1

Logic and scripting engines, which should be able to act as fast as possible to work with states delivered by higher TIER adapters.

TIER 2

Adapters which deliver data from external APIs, which are important and can change at any time

TIER 3

Adapters which are not time-critical like Visualization, Backup adapters, and adapters whose information does not necessarily need to be up-to-date. These are often schedule adapters, whose information is always a bit delayed.

[AlCalzone]

For now this is hardcoded to tier 3 to fix the current issues with chai, further improvements in the future.