ISSUE-904 - Add support for custom entries in pod /etc/hosts

[rob8714]

PR for #904

Note: Test was written with the help of one of the online Gen AI tools.

[rob8714]

@kishorv10 is something additional needed to get this merged please?

[kishorv10]

@rob8714 Our team is internally reviewing it. Can you describe the business use cases for this requirement? Probably you can add to the ISSUE. Also, are you able to deploy Pega with these changes, can you provide few screenshots if possible?

[rob8714]

@kishorv10 The use case I used it for is to integrate a device that has a self signed certificate, and the hostname in the certificate could not be added to the DNS server being used. Since the IP of the device was not in the SAN of the certificate, when sending the request over IP we were getting mismatch errors. In order not to have certificate issues due to a mismatch in hostname, we needed a way to map the IP address of the device to the hostname present in the certificate, which we did using the change submitted in this PR. Once this was done, we did not face hostname mismatch issues and the integration worked fine. This is something which is fairly simple to do on a VM by adding a hosts file entry, so the aim of the PR is to provide this functionality to containerized deployments as well.