[Provision alignment] Generate params to provision a trial

Problem

The current provisionings for GitLab.com and SM/Dedicated follow markedly distinct approaches. While SM/Dedicated relies on licenses (license key or file) to contain all needed info, GitLab.com relies on multiple syncs for a namespace.

To align the provision between the deployment types, the GitLab.com provisioning will be aligned to be similar to the SM/Dedicated. The current multiple syncs to GitLab.com will be replaced by a single sync for a namespace which includes all needed information at once. Each sync will be stored in the database on the CustomersDot side for easier auditing. These records will follow a similar behavior as the license generation for SM/Dedicated and only create a new entry for a sync if the data/info for the new sync has changed compared to the last sync. Timestamps for each sync will still be stored for a better insight into the sync frequency.

For the single sync many params have to be generated/build into a single hash. They also have to use the namespace instead of an order (most of scenarios at least). Given the current complexity, the building this hash will be split into different issues/scenarios.

Proposal

This is issue should create a new class which generates params to provision a trial plan. The class will later be used in [Provision alignment] Create service to build n... (#11448).

Result

Dedicated class to generate params for a trial plan.