Config overriding on both domain and language is complex and fragile

Drupal Version

11.2.x

Domain module version

2.0.0-beta8

Expected Behavior

I installed domain and domain_language on 11.2 - expect this to be successful

Actual Behavior

It crashed with the error reported on #3560393: Installing Domain Language Access with Domain on 11.2 can cause problems

Steps to reproduce

Run the test in Domain Language Access module or:

1. Install the standard profile
2. Use Drush to install domain and domain_language at the same time

Steps to resolve

The quick fix is to do #3560393: Installing Domain Language Access with Domain on 11.2 can cause problems but the real problem is caused by using configuration to determine domain config overrides and language config overrides at the same time. This is all happening in extremely low level code. Ideally the call to the full configuration system would not happen in \Drupal\domain\DomainStorage::prepareHostname().

There are a couple of options here:
1. Expose \Drupal\domain\DomainNegotiator::$negotiating as API so that the Domain Language Access module can do an early return when this it is called during this process. this is done on 3.x already see \Drupal\domain\DomainNegotiationContext.
2. Perhaps a better solution is to not read from the configuration system here. We could use a container parameter and determine this on container build time using \Drupal\Core\Config\BootstrapConfigStorageFactory() to not invoke config overrides.