Switch development config to use ConfigAggregator

[kynx]

Q	A
Documentation	no
Bugfix	no
BC Break	no
New Feature	yes
RFC	no
QA	no

Description

This PR changes development.config.php.dist to use a ConfigAggregator so laminas/laminas-component-installer#68 can inject --dev-only config providers. It also adds the ability to load dev-only configuration from {,*.}{global,local}-development.php files - like MVC does - so settings in the development config providers can be overridden.

I'm not sure what I can do to test these changes. As far as I can tell the existing tests don't cover the structure of the config files, but if anyone's got any pointers...

[Xerkus]

I think naming for autoloaded files would be better if shortened a bit.

Local dev configs need to be added to gitignore same as regular local config files.

[Xerkus]

You might want to rebase

[kynx]

Grrr.... done.

[kynx]

Hey @Xerkus I ended up using global.dev.php.dist instead of local.dev.php.dist - I think that's better for project-wide developer settings that get checked in to VCS.

[alexmerlin]

@kynx Do you plan to continue working on this?

[kynx]

@alexmerlin Yeah, checks are passing - remind me, what do I need to do?

[gsteel]

I think this should use "local" in the filename - the *.dist files gets checked in to VCS and convention is that *.global.* is not ignored in .gitignore whereas *.local.* is ignored - naming the file whatever.global.whatever means that when dev mode is enabled, users may end up checking in the enabled dev config, which is likely not what we want.

(And/or) The .gitignore in config/autoload probably needs updating too to exclude the dev override files: https://github.com/mezzio/mezzio-skeleton/blob/3.16.x/config/autoload/.gitignore