Adding pytest-pretty for nice test outputs

[benomahony]

Description

Closes

By Submitting this PR I confirm:

• I am familiar with the Contributing Guidelines.
• We require that all contributors "sign-off" on their commits. This certifies that the contribution is your original work, or you have rights to submit it under the same license, or a compatible license.
  • Any contribution which contains commits that are not Signed-Off will not be accepted.
• When the PR is ready for review, new or existing tests cover these changes.
• When the PR is ready for review, the documentation is up to date with these changes.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[benomahony]

@mdemoret-nv cleaned up commits + signed

[AnuradhaKaruppiah]

/ok to test eb47bc5

[AnuradhaKaruppiah]

@benomahony Thanks for the PR.
Please resolve the conflict in uv.lock using the following steps:

git fetch upstream 
git merge upstream/develop
rm uv.lock 
uv sync --all-groups --all-extras
git add uv.lock 
git merge --continue

[dagardner-nv]

LGTM, on hold for internal approvals

[dagardner-nv]

Let's use the ~= operator here, this helps us as a team track our dependencies.

Suggested change

	"pytest-pretty>=1.2.0",
	"pytest-pretty~=1.2",

[dagardner-nv]

Can you revert the white-space/formatting changes?