don't attempt to operate on configuration that may be invalid during init

[radditude]

During the init process, we order validations carefully in order to present useful errors to the user as much as possible. Over time, this has led to situations where we may intentionally suppress validation errors and operate on possibly-invalid configuration, which leads to subtle bugs and even more confusing issues - for instance, we install remote modules before returning errors about whether the module blocks are valid so that we can return errors around core version requirements before doing anything else. This leads to situations like #33745 and #33628.

For the 1.7 series, let's conduct a more comprehensive review of our init operations to ensure that the configuration we need to operate on is valid before we do anything else with it at each step during init.