Fix UFMT formatting in test_builders_utils.py

[Copilot]

Summary

The lintrunner CI job was failing due to UFMT formatting violations in the newly added backends/qualcomm/tests/test_builders_utils.py. Two function calls were split across multiple lines where UFMT requires them on a single line.

• Collapsed multi-line self._exported_program_with_get_attr(...) calls in test_is_parameter_accepts_unlifted_get_attr and test_get_parameter_reads_unlifted_get_attr to single-line form to satisfy UFMT

Test plan

Verified by the lintrunner CI job passing after the formatting fix.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22033

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

⚠️ 16 Awaiting Approval

As of commit 9d0ebc6 with merge base 90f88b7 ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build documentation (gh)
• Build Presets (gh)
• Docathon Labels Sync (gh)
• Labeler (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test Cortex-M Backend (gh)
• Test NXP Backend (gh)
• Test QNN Backend (gh)
• Test QNN Windows MSVC build (gh)
• Test Vulkan Backend (gh)
• Test WebGPU Backend (gh)
• Test XNNPACK Backend (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.