[jason810496]

Merge order:

1. Java SDK: Generate Dag and task configuration from the serialization schema #73595 — Generate Dag and task configuration from the serialization schema (current one)
2. Java SDK: Resolve a task's arguments from the Dag's own wiring #73596 — Resolve a task's arguments from the Dag's own wiring
3. Java SDK: Declare a Dag's task graph with @Builder.Deps #71189 — Declare a Dag's task graph with @Builder.Deps
4. Java SDK: Serialize native Dags to DagSerialization v3 #71190 — Serialize native Dags to DagSerialization v3

Why

Add the Dag and task level arguments, and those arguments are generated from the Airflow's own Dag serialization schema.

Example

@Builder.Dag(id = "java_etl", schedule = "@daily", catchup = false, tags = {"example"})
public class EtlPipeline {

  @Builder.Task(id = "extract", retries = 2, retryDelay = "PT5M")
  public long extract() { return 42L; }
}

The same keys on the interface surface:

var dag = new DagDef("java_etl").config("schedule", "@daily");
dag.task("extract", Extract.class).config("retry_delay", Duration.ofMinutes(5));

How

• :sdk:generateDagDsl emits org.apache.airflow.sdk.Builder — the @Builder.Dag / @Builder.Task / @Builder.TaskHandler annotations — and the key-to-type table that DagDef.config and TaskDef.config validate against.
• Field selection mirrors the Go SDK's TaskSpec generator: scalar properties only, serializer-owned keys skipped, and a documented exclusion list for Python-only concerns. An exclusion entry that stops matching an eligible key fails generation, so the list cannot go stale.
• The schema is vendored at sdk/schema/dag-schema.json so a source release builds standalone; an in-repo build refreshes it from airflow-core, and sync-java-sdk-dag-schema prek hook re-vendors it on demand.
• Annotation attributes are camelCase (retryDelay); config keys are Airflow's own names ("retry_delay").
• The generated build() constructs the DagDef itself and chains the config calls onto it.
• Durations and date-times are ISO-8601 strings in annotations, validated at compile time, and java.time values in config calls. An unknown key or a mismatched value type fails the build or Dag parsing.

---

Was generative AI tooling used to co-author this PR?

• Yes, with help of Claude Code Opus 5 following the guidelines

[FrankYang0529]

Overall LGTM. Thanks for the PR.