parameterize configuration values

Replace hardcoded configuration values with parameterized variables in build files and configuration management. This enables flexible environment-specific settings and improves maintainability.

Hardcoded values in configuration files create inflexibility and make it difficult to adapt builds for different environments or requirements. Instead, use variables that can be overridden through system properties or environment-specific configuration.

Example of improvement:

<!-- Instead of hardcoded values -->
<arg>17</arg>
<aws.java.sdk.version>1.11.655</aws.java.sdk.version>

<!-- Use parameterized variables -->
<arg>${maven.compiler.release}</arg>
<aws.java.sdk.version>${aws.sdk.version}</aws.java.sdk.version>

For dependency management, centralize version definitions in parent POM files using properties that can be easily updated and maintained. This approach allows teams to specify different versions through build parameters like -Djava.version=21 while maintaining compatibility and consistency across the project.