Initiate the TargetPlatformService module

This service accepts extension points with the following model:

Target Platforms Model

Target Platform Definition

• id (name + version)
• name (missing for now)
• version
• label
• description
• status (supported, dev, soon_deprecated, deprecated) --> this would map to permissions, maybe
• isFastTrack
• available packages ids -> see if reference per id (name + version) or if version can be implicit
• aliases (needed for target platform migration from "DM"
  to "CAP" + "DM" package for instance, can be useful for connect
  versions mappings too )
• target test nuxeo versions (5.8 + 5.8.0-HF08-SNAPSHOT for instance) --> useful for tests
• enabled (boolean allowing to enable/disable a target platform "live")
• restricted (boolean allowing to enable/disable a target platform "live" for some users only)

Target Platform Package

Different concept (packages can be referenced by target platforms) but same metadata.

Also needs a notion of "dependencies" (a package can depend on another one), this notion is not shared with target platforms for now.

Target Platform Instance

It is useful to have a notion of target platform instance (even if interface can be common to the definition) just to handle available target packages vs enabled target packages (and ask the service for a target platform definition handling the notion of "activated" packages).

Configuration

• default target platform, it's interesting not to put this boolean on the target platform definition directly in case there is additional logics to add later on (default target platform depending on some criteria for instance).
  For now only the "cap-5.8" target platform id is needed.