Ability to use the docker-compose-dev with only 1 task replica

### Please confirm the following

- [X] I agree to follow this project's [code of conduct](https://docs.ansible.com/ansible/latest/community/code_of_conduct.html).
- [X] I have checked the [current issues](https://github.com/ansible/aap-eda/issues) for duplicates.
- [X] I understand that EDA-Controller is open source software provided for free and that I might not receive a timely response.

### Feature type

New Feature

### Feature Summary

Ability to use this docker-compose file with only 1 task & podman node

https://github.com/ansible/eda-server/blob/main/tools/docker/docker-compose-dev.yaml

### Steps to reproduce

Run the docker-compose development environment.

Compare to others like [docker-compose-stage.yaml](https://github.com/ansible/eda-server/blob/main/tools/docker/docker-compose-stage.yaml)

### Current results

The -stage file allows customizing the worker count with `EDA_DEFAULT_WORKERS` but the development docker-compose does not

### Sugested feature result

I realize there may be platform differences (like running on a Mac) that may prevent `replicas:` from working correctly in every way that someone wants to use it. And for the -dev target, yeah, it makes sense to make it as flexible as possible. However, I would argue that if this should be the run-anywhere target, then it makes more sense to use 1 worker. So I'd suggest the result would be either:

- the docker-compose-dev option is configurable with the env var `EDA_DEFAULT_WORKERS`
- the docker-compose-dev option just runs 1 worker

### Additional information

_No response_

Start with tools/docker/docker-compose-dev.yaml and compare it with tools/docker/docker-compose-stage.yaml, especially how EDA_DEFAULT_WORKERS and task or podman replicas are configured. Confirm the intended single-worker behavior or environment-variable configurability, then verify the development environment starts successfully with one task replica.

Written by the indexing model from the issue text.