Configure dev/tests/integration/etc/install-config-mysql.php on M2 env initialization

[Vinai]

It would be awesome to have the integration test environment configuration happen automatically when an M2 environment is initialized.

The steps are basically listed in https://docs.warden.dev/configuration/magento2-testing.html#running-integration-tests , but I found actually only one step is required:
the one file that needs to be created is /var/www/html/dev/tests/integration/etc/install-config-mysql.php:

<?php

return [
   'db-host' => 'tmp-mysql',
   'db-user' => 'root',
   'db-password' => 'magento',
   'db-name' => 'magento_integration_tests',
   'backend-frontname' => 'backend',
   'search-engine' => 'elasticsearch7',
   'elasticsearch-host' => 'elasticsearch',
   'elasticsearch-port' => 9200,
   'admin-user' => \Magento\TestFramework\Bootstrap::ADMIN_NAME,
   'admin-password' => \Magento\TestFramework\Bootstrap::ADMIN_PASSWORD,
   'admin-email' => \Magento\TestFramework\Bootstrap::ADMIN_EMAIL,
   'admin-firstname' => \Magento\TestFramework\Bootstrap::ADMIN_FIRSTNAME,
   'admin-lastname' => \Magento\TestFramework\Bootstrap::ADMIN_LASTNAME,
   'amqp-host' => 'rabbitmq',
   'amqp-port' => '5672',
   'amqp-user' => 'guest',
   'amqp-password' => 'guest',
   'session-save' => 'redis',
   'session-save-redis-host' => 'redis',
   'session-save-redis-port' => 6379,
   'session-save-redis-db' => 2,
   'session-save-redis-max-concurrency' => 20,
   'cache-backend' => 'redis',
   'cache-backend-redis-server' => 'redis',
   'cache-backend-redis-db' => 0,
   'cache-backend-redis-port' => 6379,
   'page-cache' => 'redis',
   'page-cache-redis-server' => 'redis',
   'page-cache-redis-db' => 1,
   'page-cache-redis-port' => 6379,
];

The default config-global.php.dist file is fine, no customization is required.
The phpunit.xml.dist file works, too (even though it is far from ideal).

[stale[bot]]

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[Vinai]

I think it's still valid.