When engaging the automated restore process, a target cluster is started from a snapshot of existing data, which may potentially include persisted non-default cluster parameter settings. Cloud has indicated that they do not wish for these settings to be automatically applied on the target cluster, preferring instead that the cluster start with all default cluster parameter values that they can then manually override via the setClusterParameter command. 

To this end, we should ensure that all cluster parameter namespace(s) are dropped on the config server AND all shards during the restoration process. On non-serverless clusters, this will involve dropping the config.clusterParameters collection. On serverless clusters, this will involve dropping all namespaces matching the form <tenant_id>_config.clusterParameters (e.g., every tenant's config database has its own cluster parameters collection).

After implementing this, we should test it by creating a snapshot that includes cluster parameter collections on the config server and all shards. After the target cluster has been initialized on the snapshot data and has completed the restoration process, we should assert that running getClusterParameter individually on each cluster node (mongods and mongoses) results in default values being returned rather than the values specified in the snapshot.