[Lee HoJoon (guosasipo)]

Description

QrEncoderLib emits routine algorithm and progress diagnostics at DEBUG_INFO even when the caller passes Flags = 0. When a firmware application exports AdvancedLogger through rotating QR codes, rendering each page adds these diagnostics to the same buffer. Reopening the viewer then exports its own encoding trace, causing rapid page-count growth.

Move unconditional version, masking, penalty, format/version-bit and progress traces to DEBUG_VERBOSE. Pass the level through the private PrintBinary helper so explicitly requested QR_FLAGS_DEBUG_* output remains at DEBUG_INFO. Preserve DEBUG_ERROR and invalid-input diagnostics. No encoding algorithm or public API changes.

• Impacts functionality?
• Impacts security?
• Breaking change?
• Includes tests?
• Includes documentation?

How This Was Tested

• An out-of-tree host harness compiled the actual encoder and Mu PrintLib before and after this change. Three 752-byte, Flags = 0 inputs produced 200–220 INFO records (6,663–7,379 text bytes) per QR before the change and zero afterward; bitmap hashes matched.
• Explicit QR_FLAGS_DEBUG_ENCODING still produced INFO output; enabling DEBUG_VERBOSE recovered the routine trace. Invalid-input ERROR output was retained.
• Built and ran AArch64 DEBUG firmware on hardware. The viewer previously grew from tens to thousands of pages; repeated entry after the fix stayed at 63 pages in the comparison test. A subsequently received boot log contained no routine QR encoding traces.
• Checked with TianoCore Uncrustify 73.0.11 and the Mu Basecore configuration; no formatting differences.

The host regression harness is not included in this focused source-only change.

Integration Instructions

Enable DEBUG_VERBOSE when routine encoding traces are needed. Existing explicit QR debug flags remain supported.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.