ACPT-1599: Fixing DeploymentConfig resets & reloads every time new key that wasn't previously set

Fixing problem ACP2E-2198.
```
[Progress: 861 / 864]
Disabling Maintenance Mode:

In ResourceConnection.php line 162:

[DomainException]
Connection "default" is not defined
```

The root cause of problem is that the `Disabling Maintenance Mode` part of the install uses the first created DeploymentConfig object created in the process, which doesn't get updated, while before that runs, different part of the install that writes to the config is using the second DeploymentConfig object that was created by Laminas ServiceManager.

This commit causes Laminas' ServiceManager to use the same DeploymentConfig object as the first Magento ObjectManager used in the process, which resolves the issue seen in setup:install.

Author: JacobBrownAustin

setup/src/Magento/Setup/Console/CommandList.php

@@ -6,6 +6,8 @@
 
 namespace Magento\Setup\Console;
 
+use Magento\Framework\App\DeploymentConfig;
+use Magento\Framework\App\ObjectManager;
 use Magento\Setup\Console\Command\TablesWhitelistGenerateCommand;
 use Laminas\ServiceManager\ServiceManager;
 
@@ -16,21 +18,20 @@
  */
 class CommandList
 {
-    /**
-     * Service Manager
-     *
-     * @var ServiceManager
-     */
-    private $serviceManager;
-
     /**
      * Constructor
      *
      * @param ServiceManager $serviceManager
+     * @param DeploymentConfig|null $deploymentConfig
      */
-    public function __construct(ServiceManager $serviceManager)
-    {
-        $this->serviceManager = $serviceManager;
+    public function __construct(
+        private ServiceManager $serviceManager,
+        ?DeploymentConfig $deploymentConfig = null
+    ) {
+        $deploymentConfig ??= ObjectManager::getInstance()->get(DeploymentConfig::class);
+        /* Note: We must use same DeploymentConfig object in objects created by Laminas' ServiceManager, because
+         * some commands alter deployment configuration. */
+        $this->serviceManager->setService(DeploymentConfig::class, $deploymentConfig);
     }
 
     /**