Add support for custom MdcSerializer in EcsLayout

### Summary
`EcsLayout` from `log4j2-ecs-layout` currently uses a hardcoded implementation of `MdcSerializer` for MDC serialization. While this works well for most cases, it lacks flexibility for users with custom MDC serialization requirements.

I propose adding support for configuring or overriding the `MdcSerializer` implementation to accommodate specific use cases, such as:

- Custom JSON structure for MDC fields.
- Enhanced MDC sanitization or transformation logic.
- Integrating additional logging contexts.

### Problem Statement
The current implementation of `MdcSerializer` is resolved dynamically using `MdcSerializer.Resolver`. However, it does not allow users to provide their own `MdcSerializer` implementation.

### Proposed Solution
Introduce a mechanism to customize the `MdcSerializer`, such as already implemented for `ObjectMessageJacksonSerializer`

Empieza por EcsLayout y sigue cómo MdcSerializer.Resolver selecciona actualmente el serializador. Compara ese recorrido con la personalización existente para ObjectMessageJacksonSerializer y, a continuación, define cómo se configuraría o sobrescribiría un MdcSerializer proporcionado por el usuario. Se considera terminado cuando EcsLayout utiliza el serializador personalizado para la salida de MDC y mantiene el comportamiento predeterminado actual.

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