[Spike] Allow extensions to contribute custom convention for environment-specific operational configuration

Nadie ha tomado este issue todavía.

**Timeboxed to 2 weeks**; don't spend extra time if done earlier

Different platforms use different ways for configuring operational aspects of application in test/dev/production. LB4 should make it easy to write extensions to support these different platforms.

The goal of this spike is to find out and document what's possible today, identify gaps, propose solutions and create a list of follow-up tasks.

Few examples of operational config:
- configure datasources from environment variables
- use a faster but less-secure hashing algorithm in dev/test (a hashing algorithm is used e.g. to store user passwords)
- apply datasource configuration provided by `VCAP_SERVICES` env variable in CloudFoundry/IBM Cloud - see https://github.com/strongloop/loopback-next/pull/1574

Possibly related: https://github.com/strongloop/loopback-next/pull/983 and https://github.com/strongloop/loopback-next/issues/1396

Comienza revisando la compatibilidad actual con las extensiones de LoopBack 4 y la configuración operativa; después, lee los pull requests relacionados 1574 y 983 y el issue 1396. Documenta qué es posible actualmente, identifica las carencias, propone soluciones y enumera tareas concretas de seguimiento; la finalización consiste en el resultado documentado del spike dentro del plazo de dos semanas.

Escrito por el modelo de indexación a partir del texto del issue.