[FLINK-31947] enable stdout for flink-console.sh

[HuangZhenQiu]

What is the purpose of the change

Add stdout redirection in flink-console.sh, so that flink Kubernetes applications can fetch the stdout log in web ui.

Brief change log

• simply change on flink-console.sh

Verifying this change

Verified end to end with local build and Flink web UI in Kubernetes env.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• f9df33c Azure: FAILURE

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[wangyang0918]

Given that we are using log4j-console.properties for the log configuration, all the Flink logs will also be mirrored to the stdout. Then we will have duplicated logs for *.log and *.out.

Actually, we already have some discussion about the .out file in this PR #11839.

[HuangZhenQiu]

The file size of redirection is a concern from community. It makes sense to me. The lack of out file from web was reported by our internal users who use stream.print() to verify some execution result. Given stream.print() is a supported functionality, l feel it is a kind of lacking integrity if flink on k8s behaves differently with flink on yarn. Shall we revisit the problem together with Till and Zentol?