rdk: Unfilter passing graphics, media, and video tests in nplb_loader_filter.json

[niranjanyardi]

Unfilter verified passing graphics, window, media, and video tests from nplb_loader_filter.json.

With the Wayland display environment export fix (PR #11486), Wayland window size queries, EGL display initialization, and video/audio playback pipelines succeed on RDK.

Verified on live RDK hardware over SSH:

• SbWindowGetSizeTest.SunnyDay passes.
• MaximumPlayerConfigurationExplorerTests/* (all 10) pass.
• MultiplePlayerTest.SunnyDay passes.
• SbMediaCanPlayMimeAndKeySystem.MinimumSupport passes.
• SbMediaSetAudioWriteDurationTests/* (all 4) pass.
• SbPlayerGetAudioConfigurationTests/* (all 840) pass/skip cleanly.
• SbPlayerGetMediaTimeTests/* (all 560) pass.
• SbPlayerTest.* (all 6) pass.
• VerticalVideoTests/* passes.
• SbPlayerWriteSampleTests/* narrowed down to SbPlayerWriteSampleTests/SbPlayerWriteSampleTest.LimitedAudioInput/* (the only hung sub-suite).

Issue: 508253341

[gemini-code-assist]

Code Review

This pull request updates the test filter configuration in nplb_loader_filter.json for the evergreen-arm-hardfp-rdk platform. It removes numerous tests from the failing_tests list, including player, media, and window size tests, and refines the SbPlayerWriteSampleTest filter to only exclude LimitedAudioInput. There are no review comments, and I have no feedback to provide.

[github-actions]

🤖 Gemini Suggested Commit Message

---

starboard: Unfilter passing RDK NPLB tests

Remove verified passing graphics, window, media, and video tests from
the NPLB loader filter for the Evergreen RDK platform. These tests
now succeed following the Wayland display environment export fix,
which corrected window size queries and EGL initialization.

Verified tests include SbWindowGetSize, MultiplePlayerTest,
SbMediaCanPlayMimeAndKeySystem, and various SbPlayer functionality.
SbPlayerWriteSampleTests is now narrowed down to the specific
sub-suite that continues to hang.

Issue: 508253341

---

💡 Pro Tips for a Better Commit Message:

1. Influence the Result: Want to change the output? You can write custom prompts or instructions directly in the Pull Request description. The model uses that text to generate the message.
2. Re-run the Generator: Post a comment with: /generate-commit-message