PM2 `start` Fails When Command Contains "yaml" Or "json"

I am using PM2 to manage a python web service, initiated with a bash command.
this works:

pm2 start 'cd /home/nosson/synchronize && venv/bin/uvicorn server:app --host 0.0.0.0 --reload' --name synchronize
# [PM2] Starting /usr/bin/bash in fork_mode (1 instance)
# [PM2] Done.
# ┌────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
# │ id │ name           │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
# ├────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
# │ 0  │ synchronize    │ default     │ N/A     │ fork    │ 4917     │ 0s     │ 0    │ online    │ 0%       │ 5.8mb    │ nosson   │ disabled │
# └────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘

but when i try to specify a uvicorn log config log_config.yaml, pm2 fails to start the service:

pm2 start 'cd /home/nosson/synchronize && venv/bin/uvicorn server:app --host 0.0.0.0 --reload --log-config log_config.yaml' --name synchronize
# [PM2][ERROR] File cd /home/nosson/synchronize && venv/bin/uvicorn server:app --host 0.0.0.0 --reload --log-config log_config.yaml not found

I suspect this is due to the logic which determines if the supplied command is a pm2 config file:
https://github.com/Unitech/pm2/blob/e3a327fab7a6b385ca0d960c878347dce320ae61/lib/Common.js#L283-L294
which is called when starting the service
https://github.com/Unitech/pm2/blob/e3a327fab7a6b385ca0d960c878347dce320ae61/lib/API.js#L328

Logic for detecting config files as commands should be more precise, possibly checking if the entire command is a valid filename/path rather than a bash (or other) command

Start in lib/Common.js at the config-file detection logic linked in the issue, then trace its call from lib/API.js. Reproduce the shown pm2 start command with log_config.yaml and verify that commands containing yaml or json are not treated as config-file paths while actual config-file commands still work.