Enable Custom Public Port Configuration for Kurtosis Services in Existing Packages

[mateusfigmelo]

Currently, the default optimism package configures only internal private ports within the container and enables ephemeral ports for public ports, which limits flexibility for integration with external tools and components that rely on fixed, predictable port mappings. Many tools, especially for component communication, depend on predefined, publicly accessible ports to establish connections reliably.

Kurtosis does support both private and public port configurations when creating services, as documented here:
https://docs.kurtosis.com/api-reference/starlark-reference/service-config

However, the existing optimism package (e.g., linked code) only configures internal ports, which limits usability and integration flexibility.

Proposed Enhancement:
Introduce parameters to allow users to specify public ports explicitly. This would enable more predictable and flexible port exposure, aligning with user demands and the needs of tools that depend on fixed port mappings. Such an update would improve the package's usability in environments where deterministic port configuration is critical.