### 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. ### Proposal Create a new service to execute a sync with the info built in https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/11448+ to the new API endpoint on the GitLab side. This includes loading the correct `Order` and `subscription` object to use during the sync. Make sure to only allow the execution of the new service if the [`single_namespace_provision_sync` feature flag](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags/322/edit) is enabled. ### Result Ability to execute the new namespace sync logic.