Improve Ingress + TLS configurability

[JuryA]

Enhancements to Ingress Configuration in the Dependency-Track Helm Chart

🛠 Changes

• Ingress Template Improvement: Refined the Ingress resource configuration to better align with modern Kubernetes practices, including support for newer Ingress classes and more efficient handling of TLS configurations.
• New Configurable Values: Introduced new configurable parameters in the values.yaml file, allowing users to dynamically customize Ingress settings such as annotations, TLS secrets, and hostnames.
• Updated Documentation: Added detailed documentation within the values.yaml and README.md files to guide users on configuring the Ingress resource, emphasizing the new parameters and their impacts.

🧪 How to Test

1. Ingress Configuration:
   • Deploy the updated Helm chart into a Kubernetes environment with your specific Ingress settings.
   • Verify that the Ingress behaves as expected, handling traffic according to the new configurations.
   • Confirm that TLS termination is working correctly, if configured.
2. Documentation Review:
   • Review the updated documentation to ensure all new configurations are clearly described and easy to understand.
   • Ensure the examples provided match real-world usage scenarios for better user comprehension.

📝 Notes

• These changes aim to enhance the flexibility and usability of the Dependency-Track chart, particularly for environments requiring advanced Ingress configurations.

Close #17

[JuryA]

At the same time, you are trying to solve a real issue as pointed out in the issue, but I would prefer a new PR that don't use the bitnami dependency.

I have created a new PR, #20, and have incorporated all the points we discussed therein.

Important changes:

• Removed the Bitnami Common dependency. (@NissesSenap)
• New helper templates have been added to _helpers.tpl, including documentation where necessary. (@nscuro)
• Refactored ingress.yaml by removing the detection of the K8s API version and other related components. (@NissesSenap)
• Optimized overall to fit the intended purpose and fixed minor bugs that were found.
• Added a new extraDeploy.yaml template as a universal option for adding extra K8s resources for advanced users (which includes documentation for contributors).

May I ask to close this PR as a duplicate?