Fix TTY allocation causing missing output when backgrounding commands

[coderabbitai]

Issue Description

When running CLP package commands in the background using &, no output is printed to the console. For example:

./sbin/compress.sh ~/samples/hive-24hr &

Root Cause

The docker compose run command overrides the tty and stdin_open options defined in service configurations (source), even when neither the --no-TTY nor the --interactive flag is specified. This means docker compose run automatically sets tty: true when it detects a TTY-capable terminal and always sets stdin_open: true, regardless of the values defined in docker-compose.yaml.

Proposed Solution

1. Remove tty: true and stdin_open: true from tools/deployment/package/docker-compose.runtime.yaml to avoid confusion
2. Add --no-TTY flag to all docker compose run commands in the sbin scripts

Context

Reported by @junhaoliao in PR #1512: #1512 (comment)

[junhaoliao]

(posting the original comment here for easier record tracking)

it's found that when requesting to detach stdin from the shell using &, no output is seen in the console. e.g.,

cd build/clp-package
./sbin/start-clp.sh

# this command prints compression speed to the console
./sbin/compress.sh ~/samples/hive-24hr

# with the `&` added, no command output is observed in the console
./sbin/compress.sh ~/samples/hive-24hr &

i believe we should simply remove tty: true and stdin_open: true from the docker-compose.runtime.yaml to avoid allocating a TTY. however, removing those lines have no effects - when & is used, there's still no output printed to the console.

It was later discovered that the docker compose run command overrides the tty and stdin_open options defined in service configurations (source), even when neither the --no-TTY nor the --interactive flag is specified. In other words, if these flags are omitted, docker compose run will automatically set tty: true when it detects a TTY-capable terminal, and will always set stdin_open: true, regardless of the values defined in docker-compose.yaml. (The official documentation is unfortunately confusing and misleading on this behavior.)

then i think we should remove these two lines (rather than changing them to false) in docker-compose.runtime.yaml to avoid confusions, and add --no-TTY to all of the sbin scripts.