Template external secrets configs injection

[yardenc2003]

The current chart implementation requires static secret and configmap names to be provided in various mount-related values (envFrom, additionalVolumes, secretMounts, etc.).

This creates a challenge when the Trino chart is deployed as part of a parent chart, with multiple deployments in the same namespace.
Similar to the Trino chart (which uses {{ template "trino.fullname" . }}- for unique resource names), the parent chart resource names are often rendered according to release-specific values, so the static naming requirement for these mounts of resources external in the Trino chart creates a limitation in such scenarios.

Similar PRs have been raised in the past, including one I previously opened and closed because the use case wasn’t sufficiently justified at the time. In this case, however, the justification is clear: the current implementation prevents deploying a parent chart multiple times in the same namespace when Trino is a subchart, which I believe is a common use case.

I’ve updated the tests to demonstrate that the templating works correctly for resource names. However, the coverage may not include all the tpl changes I’ve introduced. Please let me know if additional test updates or further modifications are needed.

[shohamyamin]

This will be great especially when you want to have several Trino clusters as sub charts with a gateway in the same chart