fix: respect the user-provided log options regardless of tracing configuration

[RobGeada]

Description

Using tracing overrides all user-provided logging configuration. While this is necessary to generate detailed logs, it should not require returning that new log information back to the user if they did not request it. See #1316 for more detail.

Changes:

1. Ensures that regardless of tracing configuration, the returned response object respects the requested log options.
2. Modifies existing tracing unit test to account for new logging behavior
3. Adds new tracing unit test to check that ll permutations of logging options are respected if tracing is configured.

Related Issue(s)

• Implements feature: Disentangle tracing and logging #1316

Checklist

• I've read the CONTRIBUTING guidelines.
• I've updated the documentation if applicable.
• I've added tests if applicable.
• @mentions of the person or team responsible for reviewing proposed changes.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.60%. Comparing base (bee719b) to head (008e17e).
⚠️ Report is 11 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1317      +/-   ##
===========================================
+ Coverage    70.45%   70.60%   +0.15%     
===========================================
  Files          161      161              
  Lines        16214    16302      +88     
===========================================
+ Hits         11423    11510      +87     
- Misses        4791     4792       +1     

Flag	Coverage Δ
python	70.60% <100.00%> (+0.15%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
nemoguardrails/rails/llm/llmrails.py	90.09% <100.00%> (+0.65%)	⬆️

... and 4 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull Request Overview

This PR fixes an issue where tracing configuration was overriding user-provided logging options in the response object. The change ensures that when tracing is enabled, comprehensive logging occurs internally for tracing purposes, but the returned response respects the user's original log configuration preferences.

• Stores original user log options before tracing modifications
• Filters response log data to match user's original preferences
• Updates tests to verify new behavior across all logging option combinations

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
nemoguardrails/rails/llm/llmrails.py	Adds logic to preserve original log options and filter response data accordingly
tests/test_tracing.py	Updates existing tests and adds comprehensive parametrized test for all log option combinations

[Pouyanpi]

@RobGeada Great job! Thank you very much for this PR, it looks good!
Would you please look at the open comments and resolve them.

I think this PR is in a good shape to include it for 0.16.0 release.

A minor note; please make sure all your commits are gpg signed following contributing guidelines.

[RobGeada]

@RobGeada Great job! Thank you very much for this PR, it looks good! Would you please look at the open comments and resolve them.

I think this PR is in a good shape to include it for 0.16.0 release.

A minor note; please make sure all your commits are gpg signed following contributing guidelines.

Hi @Pouyanpi, thanks for the review- I've addressed the comment and have rebased the branch onto a signed commit.