UefiDbgExt: apply cpp uncrustify formatting

[VivianNK]

Preface

Please ensure you have read the contribution docs prior
to submitting the pull request. In particular,
pull request guidelines.

Description

<Please include a description of the change and why this change was made.>

For each item, place an "x" in between [ and ] if true. Example: [x].
(you can also check items in the GitHub UI)

• Impacts functionality?
  • Functionality - Does the change ultimately impact how firmware functions?
  • Examples: Add a new library, publish a new PPI, update an algorithm, ...
• Impacts security?
  • Security - Does the change have a direct security impact on an application,
    flow, or firmware?
  • Examples: Crypto algorithm change, buffer overflow fix, parameter
    validation improvement, ...
• [ x] Breaking change?
  • Breaking change - Will anyone consuming this change experience a break
    in build or boot behavior?
  • Breaks Uncrustify check on header files. Dependent on mu_basecore change (Cherry pick and apply uncrustify changes mu_basecore#609)
• Includes tests?
  • Tests - Does the change include any explicit test code?
  • Examples: Unit tests, integration tests, robot tests, ...
• Includes documentation?
  • Documentation - Does the change contain explicit documentation additions
    outside direct code modifications (and comments)?
  • Examples: Update readme file, add feature readme file, link to documentation
    on an a separate Web page, ...

How This Was Tested

<Please describe the test(s) that were run to verify the changes.>

Integration Instructions

<Describe how these changes should be integrated. Use N/A if nothing is required.>

[makubacki]

My understanding is that this code is largely derived and/or relatable to another source. Given that, it may be detrimental to maintenance to introduce unnecessary deviation. In addition, the Uncrustify rules are intended for firmware code so it's a bit ambiguous if they should apply here (to a WinDbg extension). I'm also not aware of an effort to actively run Uncrustify against this code in CI like the firmware code meaning the formatting will not be upheld over time losing its original purpose.

Without any additional context about the change, for those reasons, I lean toward not applying these Uncrustify rules to this code at this time.