ci: group behavior test setups by service

[rohankumardubey]

Which issue does this PR close?

Closes #7919.

Rationale for this change

Behavior-test configurations currently run as separate jobs, exceeding ASF concurrency guidelines. Grouping configurations by service reduces concurrent jobs while preserving coverage.

What changes are included in this PR?

• Group core behavior-test setups by service.
• Run grouped setups sequentially in one job.
• Isolate Docker resources and environment variables between setups.
• Preserve Windows filesystem coverage.
• Add planner and testkit regression tests.

Are there any user-facing changes?

No. This change only affects CI behavior tests.

[erickguan]

Nice progress! Can we also group a related test?

e.g.,

• 0_minio_s3
• minio_s3_with_annoymous

create a group so we can toggle them?

[rohankumardubey]

@Xuanwo @tisonkun can you please review this.

[erickguan]

Hi @rohankumardubey,

Thank you for working on this. Can you resolve the failure from redis? Perhaps you can try to list the folder or print contents in the folder in a debug block?

[rohankumardubey]

Hi @rohankumardubey,

Thank you for working on this. Can you resolve the failure from redis? Perhaps you can try to list the folder or print contents in the folder in a debug block?

@erickguan Thanks for the pointer. The Redis TLS setup ran a nested checkout, which cleaned the workspace and deleted the remaining generated test actions. I removed the redundant checkout from both Redis TLS setups and added a regression test to prevent this from recurring.

[erickguan]

Thanks for improving OpenDAL's CI!