feat: Parse YAML parameters sequentially.

[redscholar]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Variables are parsed and stored on a per-host basis during playbook execution.
The parsing priority when using YAML v3 to evaluate variables is as follows:

- name: playbook
   host:
    - localhost
   vars_files:
    - file1
    - file2
   vars:
     a: b

Priority Order (highest to lowest):

1. vars (e.g., a: b)
2. file1 (first in list)
3. file2 (last in list)

Note: If a later-defined variable conflicts with an earlier one, the later value overrides the earlier definition.

Which issue(s) this PR fixes:

Fixes # #2496

Special notes for reviewers:

Does this PR introduced a user-facing change?

Parse YAML parameters sequentially.

Additional documentation, usage docs, etc.:

[kubesphere-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: redscholar

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [redscholar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sonarqubecloud]

Quality Gate failed

Failed conditions
6.0% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud