Pass task required properties from overlord to task pod

### Description


As stated by the [doc](https://druid.apache.org/docs/latest/development/extensions-contrib/k8s-jobs#migrationkubernetes-and-worker-task-runner) above, these two properties should be configured to peon tasks.

However, these two properties should be only present at the overlord side to create a task POD, and if task pod really needs these two properties, overlord should pass these two to task POD in the background for users.

Managing thes properties in K8S is tedious, because we have to keep two copies of these properties, one at the overlord side, another at the peon side.

Removing these two from peon would help ease the configuration.

Start with the linked Kubernetes and Worker Task Runner migration documentation and identify the two properties referenced there; the issue does not name their keys or implementation files. Trace how the Overlord creates the task pod, then verify that users configure the properties only on the Overlord while the pod still receives them automatically.

Written by the indexing model from the issue text.