Remove unnecessary configuration in Queue Processor mode

[johngmyers]

Issue #, if available:

None

Description of changes:

Remove configuration settings that don't affect Queue Processor mode (assuming #743 merges) from the Deployment template, so that they don't act as red herrings.

Document the settings that only apply to IMDS mode.

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

[snay2]

This is incorrect. The probes server can be exposed whether NTH runs as a daemonset or as a deployment and is not related to IMDS mode. Our default configurations here only enable it for the daemonset, not the deployment, but that is not a technical limitation.

Indeed, our release artifacts explicitly include an aggregated YAML configuration with probes server enabled in Queue Processor mode as a deployment (see the artifact all-resources-queue-processor.yaml from any v1 release). Here's the code that generates that file:

aws-node-termination-handler/scripts/generate-k8s-yaml

Lines 61 to 66 in c3e411b

	## Queue Processor Mode
	$BUILD_DIR/helm template aws-node-termination-handler \
	--namespace $NAMESPACE \
	--set enableSqsTerminationDraining="true" \
	--set enableProbesServer="true" \
	$SCRIPTPATH/../config/helm/aws-node-termination-handler/ > $QP_AGG_RESOURCES_YAML

[snay2]

To be more correct, let's remove "for the Daemonset", since the probes server can be used in a deployment and is not related to IMDS mode.

Suggested change

	# If the probes server is running for the Daemonset. Only used in IMDS mode.
	# If the probes server is running