[codex] Fix release-mode binding regressions

[Xueyang-Song]

Summary

• Replaced trim-fragile loose-template/property-path bindings with code-backed presenters across release-broken UI surfaces.
• Restored issue and pull request filtering by moving filter templates behind presenters, explicitly committing Apply/Clear values, resetting stale request state, and wiring issue label filters.
• Added public-preview issue/PR filter handling so packaged release smoke tests can exercise filter behavior without depending on GitHub API state.
• Added a XAML binding pattern regression test to catch the release-mode binding shape that caused these failures.

Root Cause

Release trimming was breaking untyped XAML binding paths in loose templates and related UI surfaces. Debug mode kept enough reflection metadata around for those bindings to appear healthy, but packaged Release lost binding data, leaving controls blank or non-functional. Some filters also held stale request objects between Apply/Clear, so even working controls could leave old filter parameters behind.

Validation

• dotnet test JitHub.WinUI.Tests\JitHub.WinUI.Tests.csproj -c Release -p:Platform=x64 passed, 92/92.
• dotnet build JitHub.WinUI\JitHub.WinUI.csproj -c Release -p:Platform=x64 succeeded with the existing SvgPreview trim warning.
• Packaged Release smoke: PR State, PR Head, Issue State, and Issue Labels filters applied and Clear restored lists without crashing.
• Windows Application event log showed 0 JitHub crashes since the final packaged launch.