fix(win): Windows.Graphics.Capture API frame rate capped at 60fps

[StringWeaver]

Description

Typically Windows Gaphics Capture API has a lower latency and better compatibility with DLSS-FG than Desktop Duplication API, but capped at 60 fps due to some internal limitation.
I fixed it by calling MinUpdateInterval(), like many other GitHub projects. I tested it on my computer and comfirm it can let frame capture running at 120Hz(which is my client setting)
Test environment: Windows 11 Version 26200.6584

Screenshot

Before:

After:

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes

[codecov]

Bundle Report

Bundle size has no change ✅

[codecov]

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 14.22%. Comparing base (a2e6fc9) to head (ca39a0f).
⚠️ Report is 123 commits behind head on master.

Files with missing lines	Patch %	Lines
src/platform/windows/display_wgc.cpp	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4424      +/-   ##
==========================================
- Coverage   14.23%   14.22%   -0.02%     
==========================================
  Files          89       89              
  Lines       18936    18942       +6     
  Branches     8677     8682       +5     
==========================================
- Hits         2696     2694       -2     
- Misses      12963    15237    +2274     
+ Partials     3277     1011    -2266     

Flag	Coverage Δ
FreeBSD-14.3-aarch64	?
FreeBSD-14.3-amd64	13.53% <ø> (-0.02%)	⬇️
Linux-AppImage	11.55% <ø> (ø)
Windows-AMD64	13.33% <0.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/platform/windows/display_wgc.cpp	0.00% <0.00%> (ø)

... and 45 files with indirect coverage changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud