feat: sync internal release-0910 improvements

[lkygithub]

Description

• Add persistent job log collection and querying with Fluent Bit and Aliyun SLS, including pagination, filtering, system configuration, and credential masking.
• Improve the job lifecycle experience with job.phase-based status, clearer FailedScheduling diagnostics, image-matched pull progress, selectable and copyable details, task ID and node filters, and recent-image suggestions.
• Expand workload storage and access options with per-PVC size settings, a 200 GiB frontend limit, simplified StorageClass handling, multiple SSH keys, and Pod SSH login.
• Tighten task and role naming validation, optimize API and network connections, streamline dev-init handling, fix the rclone CSI manifests, and add a development-container setup.
• Update generated CRDs and clients, English and Chinese documentation, and automated tests for the affected behavior.

Motivation and Context

Source mapping:

• Previous synchronized internal tag: release-0901 (22bf783e26342e02df4eb1bb3d35ca6775beb9eb)
• Internal source tag: release-0910 (6c18604b826bb8f0114c84be1c5b0b008943634c)
• Public base: main (5f85f45315d839d3e8466a4efb04a6d0a8ae4725)
• Public candidate commit: cfa06ac8d0a0f2f0136b1f9be5f4e7a1d5d2fc50

How has this been tested?

• GitHub Actions validation on the exact candidate tree:
  • commit and PR-title checks
  • Go lint for api, apps/embodied-runtime, and apps/rlark
  • frontend and documentation lint
  • unit tests for api, apps/embodied-runtime, and apps/rlark
  • Docker builds for RLark, embodied-runtime, and the frontend
• Frontend standalone test suite: 67/67 tests passed with npm test.
• Patch and whitespace validation completed successfully.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation update
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.