Customer feedback | az containerapp job (both Core and Extension) | Warning about behavior of job start #

### Describe the bug

This GitHub issue is being moved from MicrosoftDocs/azure-docs-cli [GitHub issue #4456](https://github.com/MicrosoftDocs/azure-docs-cli/issues/4456).

*******************************
**Type of issue**
Missing information

**Feedback**
The documentation should be enhanced by including a cautionary note regarding the start of a new job and overridden configuration. In particular, based on my examinations:

Emphasize that options such as --command, --args, --env-vars, etc., are functional only when used in conjunction with --image
Referring to the [documentation](https://learn.microsoft.com/en-us/azure/container-apps/jobs?tabs=azure-cli#start-a-job-execution-on-demand), note that "When overriding the configuration, the job's entire template configuration is replaced with the new configuration. Ensure that the new configuration includes all required settings.". Therefore, the statement "Empty string to clear existing values" on certain parameters may be misleading, as in my assessments, the environment variables specified by the container are cleared even in the absence of the --env-vars parameter.

**Page URL**
https://learn.microsoft.com/en-us/cli/azure/containerapp/job?view=azure-cli-latest

**Content source URL**
https://github.com/MicrosoftDocs/azure-docs-cli/blob/main/latest/docs-ref-autogen/containerapp/job.yml
********************************************

### Related command

az containerapp job

### Errors

n/a

### Issue script & Debug output

n/a

### Expected behavior

n/a

### Environment Summary

n/a

### Additional context

n/a