test: Move initializer_as_input ONNX test into qa/ and drop cpdir

[Vinya567]

What does the PR do?

Moves the initializer_as_input ONNX QA test from onnxruntime_backend/test/ into qa/L0_initializer_as_input/ so the test lives in the same repo where it's consumed by the QA harness (and follows the existing L0_ tier naming convention under qa/). Drops the now-redundant cpdir(onnxruntime_backend/test/*, qa/) line from cibase_build() in build.py — the files are already part of the qa/ checkout, so the cross-repo wildcard copy is unnecessary.

This addresses the [WIP] other way than wildcard? comment that was left when the cross-repo cpdir was originally introduced.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

• test

Related PRs:

• Follow-up PR in triton-inference-server/onnxruntime_backend to remove the now-duplicated test/initializer_as_input/ directory (will be opened after this PR merges so the source-of-truth in qa/ is live first).

Where should the reviewer start?

1. build.py — the 3-line deletion in cibase_build() is the actual behavioral change. Confirm nothing else in that function depends on qa/ being repopulated from the backend tree.
2. qa/L0_initializer_as_input/ — the migrated test. Files are byte-identical to the originals in onnxruntime_backend/test/initializer_as_input/; no logic changes. Diff is effectively a cross-repo directory move + L0_ prefix to match the qa/ naming convention.

Test plan:

1. Local run of test.sh inside nvcr.io/nvidia/tritonserver:26.04-py3 with the new qa/L0_initializer_as_input/ mounted as the working directory:
   • tritonserver starts, loads add_with_initializer
   • test.py issues an inference request and verifies output
   • Result: PASS (exit code 0)
2. CI run with the cross-repo cpdir removed and the test sourced from qa/:
   • py3-devel builds successfully (proves build.py change does not break the dev image build)
   • L0_initializer_as_input--ONNXRuntime passes, pulling files from the qa/ checkout (no cross-repo wildcard)
   • All other jobs in the gating set are green

• CI Pipeline ID: 55844627

Caveats:

• NVIDIA's downstream RHEL build currently copies onnxruntime_backend/test/ into qa/ at image-build time (added recently as a hotfix to unblock the RHEL pipeline). That copy becomes a no-op once this PR merges, since qa/L0_initializer_as_input/ is already in the build context. A follow-up cleanup will remove it from the downstream Dockerfile.
• The old onnxruntime_backend/test/initializer_as_input/ directory is intentionally kept in place until this PR lands, so the existing cross-repo flow stays functional during review.

Background

The cpdir line being removed was originally added in #5630 with a [WIP] other way than wildcard? comment, flagging that the cross-repo wildcard copy was a temporary stopgap. Since qa/ is the canonical location for QA tests consumed by Triton server's QA harness, the cleanest fix is to land the test where it's consumed and drop the wildcard.

Related Issues:

N/A — no public github issue tracking this cleanup.

[whoisj]

LGTM, concerned about the copyright on each file. Please address (explain or correct).

[Vinya567]

LGTM, concerned about the copyright on each file. Please address (explain or correct).

These aren't actually new , they're moves from onnxruntime_backend/test/initializer_as_input/ where they've existed since 2023. So the 2023 in the header is the original authorship year, and 2026 is when I moved them here.

Worth noting: the pre-commit add-license hook produced this 2023-2026 automatically when I amended ,it picks up the original year and extends to today. The tool itself follows the same pattern (its own header at tools/add_copyright.py line 1 reads "Copyright (c) 2024-2026").