Feature Request: Support container command and args configuration

Currently, the Azure/container-apps-deploy-action does not provide a clean way to configure:

template.containers[].command

template.containers[].args

This forces users to:

Manually call az containerapp update

Or modify configuration in the Azure Portal

Or use --set template.containers[0].command=...

This creates:

Drift between CI and Portal configuration

Parsing inconsistencies with --args

Difficulty managing runtime commands for worker workloads (e.g., Celery)
Use Case

For example, running a Celery worker:

python -m celery -A src.celery_app:celery worker --loglevel=info --pool=threads

In Azure Container Apps, this requires setting:

"command": ["python"],
"args": [
"-m",
"celery",
"-A",
"src.celery_app:celery",
"worker",
"--loglevel=info",
"--pool=threads"
]

There is currently no native way to define this via the deploy action.

Requested Enhancement

Add support for something like:

with:
command: |
python
args: |
-m
celery
-A
src.celery_app:celery
worker
--loglevel=info
--pool=threads

Or:

with:
command: ["python"]
args: ["-m","celery","-A","src.celery_app:celery","worker","--loglevel=info","--pool=threads"]