[fix](docker) Fix doris-compose up without env argument

[wyxxxcat]

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary: In 4.1.2-tmp-rc03 release regression, Docker Case and S3 Docker Case failed broadly during docker-compose cluster startup. The storage vault snapshot change reads args.env in doris-compose.py up to check ENABLE_STORAGE_VAULT, but the affected release branch can run with an argparse Namespace that does not define env. This causes AttributeError: 'Namespace' object has no attribute 'env' before the test cluster is created, blocking docker-based regression suites.

This change reads the optional env argument with getattr(args, 'env', None) once and reuses that value for both ENABLE_STORAGE_VAULT parsing and Cluster.new(). When the argument is absent, the default behavior is unchanged: no extra environment variables are passed and storage vault remains disabled.

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[wyxxxcat]

run buildall

[deardeng]

LGTM

[wyxxxcat]

/review

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.

[github-actions]

Static review completed for PR 65142.

Scope: one Docker runtime helper change in docker/runtime/doris-compose/command.py. The patch fixes up callers whose argparse Namespace lacks env by reading it through getattr once and reusing the same value for storage-vault detection and Cluster.new().

Checkpoint conclusions:

• Goal/test proof: The code addresses the Namespace compatibility failure. I verified the changed Python files compile with python3 -m py_compile docker/runtime/doris-compose/command.py docker/runtime/doris-compose/cluster.py docker/runtime/doris-compose/doris-compose.py; full docker runtime/regression tests were not run because this checkout lacks .worktree_initialized, thirdparty/installed, and local runtime imports are missing filelock/jsonpickle.
• Scope/focus: The change is small and limited to optional env propagation in new-cluster creation.
• Concurrency/lifecycle/transactions/persistence/protocol: Not applicable; this does not add concurrency, lifecycle ownership, transaction behavior, persistent format changes, or FE/BE protocol changes.
• Config/session compatibility: Cluster.get_env_value() already tolerates None, Node.docker_env() ignores missing/empty env lists, and user envs still override generated node envs when present.
• Parallel paths/coverage: Existing-cluster up does not consume args.env, and no optimizer/rewrite paths are touched.
• Observability/performance: No new observable behavior or hot-path work.

User focus: no additional user-provided review focus.

Subagent conclusions:

• optimizer-rewrite: no optimizer/rewrite candidates; the change does not touch planner, join, aggregate, or semantic rewrite paths.
• tests-session-config: no tests/session/config candidates; static syntax validation passed, with runtime validation limited by missing local dependencies noted above.

No inline review comments are needed.