Creating a Deployment defaults to "Allow Privilege Escalation"

[gaktive]

Internal reference: SURE-3663

Request description:
When users create Deployments in the Rancher Cluster Explorer UI, the setting under "Security Context" -> "Privilege Escalation" defaults to "Yes, container can gain more privileges than its parent process"

Users will fail to create deployments by default (at least when e.g. setting the "Run as User ID" field). The security context parameter is not added to the deployment unless one parameter is set, however when some parameter is set the Privilege Escalation option is set to yes by default.

This could be considered a more secure means of running Kubernetes, which would help with RKE2 strategy to align with other usage within the product.

Actual behavior:
Privilege Escalation in the security context tab is set to yes by default

Expected behavior:

Privilege Escalation in the security context tab is set to no by default

Additional notes:
Instead of choosing between one default or another, it would be helpful to have a way to select the default config options in the UI for each user.

[nickwsuse]

Verified on v2.7-head Commit ID: c35f112

The Privilege Escalation field is now defaulted to the No option.