test: Add tests for the Triton log callback

[pskiran1]

What does the PR do?

Adds QA coverage for the log callback feature. Builds and runs the common logging_test as part of L0_logging, and runs the new test_logging_callback.py in L0_python_api.

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 ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

• https://github.com/triton-inference-server/dynamo/pull/2
• feat: Add log callback option to tritonserver C and Python APIs core#504
• feat: Support a log callback in the common Logger common#158

Where should the reviewer start?

Test plan:

• CI Pipeline ID: 57710794

Caveats:

Background

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• closes GitHub issue: #xxx

[greptile-apps]

Greptile Summary

This PR wires up QA coverage for the Triton log-callback feature: the logging_test gtest binary (built by triton-inference-server/common#158) is added to the Docker QA image and executed at the end of L0_logging, and test_logging_callback.py (landed via triton-inference-server/core#504) is exercised through L0_python_api. No logic or server code is changed.

• Dockerfile.QA: copies bin/logging_test into qa/L0_logging/ inside the cibase stage; requires the binary to be present in CIBASE_IMAGE at build time.
• qa/L0_logging/test.sh: appends a gtest run of ./logging_test after all existing server-based log tests, using set +e/set -e guards and RET accumulation consistent with the file's existing pattern.
• qa/L0_python_api/test.sh: adds a fourth pytest block for test_logging_callback.py, matching the structure of the three existing blocks above it.

Confidence Score: 5/5

Safe to merge once the dependent PRs (common#158 and core#504) that produce the binary and the Python test file have landed in the base image.

All three changed files are purely additive test wiring with no server logic or data-path changes. The new code follows the exact same error-accumulation and set+e/set-e patterns used throughout both test scripts.

No files require special attention beyond confirming that the common#158 and core#504 related PRs have merged before running CI.

Important Files Changed

Filename	Overview
Dockerfile.QA	Adds cp bin/logging_test qa/L0_logging/. to distribute the gtest binary into the QA image; depends on binary being present in CIBASE_IMAGE.
qa/L0_logging/test.sh	Appends a gtest-based logging_test run at the tail of the logging test suite; uses >> for log redirection while the existing log_format_test block uses >.
qa/L0_python_api/test.sh	Adds a pytest invocation of test_logging_callback.py after the kserve test block; consistent pattern with the three existing pytest invocations in this file.

_{Reviews (5): Last reviewed commit: "Update" | Re-trigger Greptile}