Log NVDA app architecture at startup

[josephsl]

Link to issue number:

Closes #16432

Summary of the issue:

NVDA does not log its own app architecture at startup.

Description of user facing changes

NVDA's app architecture will be logged as part of the log at startup.

Description of development approach

At startup, log os.environ["PROCESSOR_ARCHITECTURE"], useful if running NVDA on 64-bit systems and to prepare for #16304 work.

Testing strategy:

Manual testing: compare log output between before (prior to this PRE) and after (merging this PR).

Known issues with pull request:

None

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.