Clarify 2 GB RAM FAQ: licensing state, not activation grace expiry

[xoere2]

Clarify the "2 GB RAM on a new Windows Server VM" FAQ entry

What

Rewrites the FAQ answer "My memory is limited to 2 GB on a new Windows Server VM" in
support/azure/virtual-machines/windows/windows-virtual-machine-activation-faq.yml.

Why

The current answer says "Windows activation has a significant impact on the amount of hardware
recognized in terms of RAM/processor." This is directionally correct (completing activation fixes it)
but imprecise, and sitting directly beneath the "What happens if the Windows activation period expires?"
entry it invites readers to conclude that an expired grace period reduces RAM. It does not:

• The RAM/CPU ceilings are edition-specific licensed limits applied from the Windows licensing
  (product policy) state that is established when the guest OS is correctly licensed and activated.
• The 2 GB report is a conservative fallback that appears when a new VM's licensing was never
  successfully established (for example, the guest OS could not reach the activation/KMS endpoint
  during provisioning).
• An expired grace period on an already-licensed VM produces activation notifications only
  (consistent with the preceding FAQ entry and the linked Licensing Conditions page); it does not
  reduce RAM or CPU.

Change

• Broadens the question to mention reduced CPU count (the existing answer already referenced
  "RAM/processor").
• Replaces the one-line answer with a short explanation that separates licensing/provisioning state
  from grace-period expiry, and keeps the same resolution (complete activation: reach Azure KMS,
  correct KMS client setup key or Azure Hybrid Benefit, then restart).

No new product behavior is asserted; wording uses publicly documented Windows licensing concepts only.

[prmerger-automator]

xoere2 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. Jarrett Renshaw (@JarrettRenshaw)@JusilverMSFT

[learn-build-service-prod]

Learn Build status updates of commit 35ceea4:

✅ Validation status: passed

File	Status	Preview URL	Details
support/azure/virtual-machines/windows/windows-virtual-machine-activation-faq.yml	✅Succeeded

For more details, please refer to the build report.

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.

[JusilverMSFT]

Looks good to me.

Discussed this on the side with engineer on the change request side.