[aws-node-termination-handler]: Use hostPort only with hostNetwork

[hwoarang]

Description of changes

There is no need to use the hostPort option if we are not directly
connected to the hostNetwork. Using the hostPort option makes that port
unavailable for binding to any other service on the node which is
not really desirable if the pod itself is not on the host network.

Checklist

• Incremented the chart version in Chart.yaml for the modified chart(s)
• Manually tested. Describe what testing was done in the testing section below
• Make sure the title of the PR is a good description that can go into the release notes

Testing

No testing was done apart from checking with helmTemplate that no hostPort is
present in the rendered files when useHostNetwork is not enabled.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[bwagner5]

Sorry for the delay! We only take PRs to NTH through the application's repo here https://github.com/aws/aws-node-termination-handler , this allows us to run our suite of e2e tests and then we sync over the chart to eks-charts when we release NTH . Would you mind opening this PR in that repo?

The changes look good here. When you do open the PR in the NTH repo, you can drop the chart version change since it will automatically be incremented when we sync the chart here. Thanks!