v3-cli: ddn connector init Hint Changes

### Component

### What is the current behaviour?
After Running the `ddn connector init` command in the out it will give you the hint to run as a separate container

HINT Run Connector: docker compose -f bug_bounty/connector/airplans/compose.yaml watch

### What is the expected behaviour?

If we run this command and after that rebuild the v3 with
`HASURA_DDN_PAT=$(ddn auth print-pat) docker compose up --build -d ` this will error out with
`Bind for 0.0.0.0:8085 failed: port is already allocated` since they run on different network so its always recommended to run `docker compose up --build -d` instead to running docker compose separately

### Any possible solutions/workarounds you're aware of?

Change the HINT to suggest to run
`docker compose up --build --watch`

Start at the `ddn connector init` command's hint output and compare the current Docker Compose instruction with the expected combined command. Update the hint to recommend `docker compose up --build --watch`, then verify that the generated guidance no longer suggests running the connector separately.

Written by the indexing model from the issue text.