Analyze and Optimize Docker Compose Memory Usage for ID-Repository #1649

Description
Investigate the high memory consumption observed when running the ID-Repository application locally using Docker Compose.
On a fresh application startup, the overall Docker Compose memory usage exceeds 2 GB. Some of the major memory consumers currently observed are:
mosip-config: ~685 MB
keymanager: ~585 MB
Analyze why these supporting services and the overall Docker Compose setup consume high memory and identify possible optimizations to reduce the local resource footprint without affecting functionality.

Scope
Analyze memory consumption of all containers started through the ID-Repository Docker Compose setup.
Investigate why mosip-config consumes approximately 685 MB.
Investigate why keymanager consumes approximately 585 MB.
Check JVM heap settings (-Xms, -Xmx, container-aware JVM settings, etc.).
Check Docker Compose memory/resource configurations.
Identify unnecessary services or components being started for local ID-Repository development.
Check whether service configurations can be optimized for local development.
Compare memory usage during startup and after the application reaches a stable/idle state.
Identify and implement feasible memory optimizations without impacting ID-Repository functionality.