Bug: New Service replacement fails at service provider precedence on core factory implementations

[element-code]

When a core service factory implementation calls another service (which should be overwritten by an app or module service), the service provider precedence doesn't work.

When CodeIgniter\Config\Services::exceptions() is called it internally calls static::response().
As of #3943 this should again check for response service factories in all service providers. Instead, the core factory static::response is used.
Tl;dr: Right now we can't replace services when they are called in core factories.
Workaround: Let Config\Services extend CodeIgniter\Config\Services , as done before.

CodeIgniter 4 version
development

Affected module(s)
Services

Expected behavior, and steps to reproduce if appropriate
All service providers should never call static::foobar() as this ignores the service provider precedence.
Instead, there should be a simple way to fetch the right service provider / service.

Reproduce

1. Provide an own response service via any service provider
2. Call in your controller:

dd(
	$this->response, 
	Services::response(NULL, FALSE), 
	Services::response(NULL,TRUE)
); 

3. the shared instance is the system instance (since it got created while CI boot through the exceptions service).
   When creating a new instance from the config service provider we get the right service.
   

[element-code]

@MGatner is the right way to get a service always to call \App\Config\Service::foobar() \Config\Service::foobar()?

[MGatner]

Right idea but it is actually \Config\Services::service() because of Config's special namespace. Also theoretically I could see wanting to access a service without lookup from System services directly, but we should never do that in the framework.

The helper function service() is basically a convenient way to do the former.

[element-code]

So then i replace all parent::foobar() calls in CodeIgniter\Config\Services?

[MGatner]

I think it should be static::foobar() that is replaced with Services::foobar().

[element-code]

Yeah 🤦‍♂️🤦‍♂️🤦‍♂️