Improve pipectl install command to be able to deploy Cloud-Pipeline out of point-in-time configuration

[SilinPavel]

trafficstars

Approach Based on #3588 results let's implement a way to specify such directory as an input for pipectl install command.

• If such option (-pc/--point-in-time-configuration) was provided, install command should be launched with:
  • List of service from cp-serices.json enabled
  • cp-config-global.properties should be used as install-config
  • dockers-manifest from point-in-time configuration should be used instead of inner dockers-manifest from pipectl binary
    • Bear in mind that dockers-manifest from point-in-time configuration has slightly different structure (additional level in directory structure due to docker-registry folder) So, code should be adjusted to be able to work with both versions of dockers-manifest folder
  • system-preferences.json should be used on the final stage of the installation. install process should iterate over this list and update corresponding items with these values.

[SilinPavel]

Let's introduce additional option (should take effect only when -pc/--point-in-time-configuration enabled) -pcm/--point-in-time-configuration-modules (example of possible value: services,tools) depending on this setting we will define which modules we should grab and apply from pitc:

• if -pcm isn't present - apply all all modules
• else - check that module is enabled in this setting

[SilinPavel]

Let's also change approach to save registered users: Instead of use GET /users let's use POST /user/export with all flags enabled

Then let's use this csv file in pipectl install from pitc and utilize POST /users/import method to register this list of users, if configured