rdk: remove dangling raspi reference

[anshugupta27]

The starboard/raspi directory has been deleted as part of the raspi-2 deprecation. This removes the dangling reference to //starboard/raspi/shared/system_gles2.cc for the rdk-rpi target.
Bug: 500021808

[github-actions]

🤖 Gemini Suggested Commit Message

---

Error: Could not parse a valid response from the Gemini API. Please check the API response logs in the workflow run.

---

💡 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

[gemini-code-assist]

Code Review

This pull request removes support and references for the Raspberry Pi (raspi/raspi-2) platform across configuration, test, and build files. The review feedback points out that removing the rdk-rpi specific system_gles2.cc override in BUILD.gn could break the rdk-rpi target if it is still supported, and suggests either moving the Raspberry Pi-specific GLES initialization code to the rdk directory or cleaning up the rdk-rpi target entirely.

I am having trouble creating individual review comments. Click here to see my feedback.

starboard/contrib/rdk/src/third_party/starboard/rdk/shared/BUILD.gn (299-306)

Simply removing the rdk-rpi specific system_gles2.cc override will cause the rdk-rpi target to fall back to the generic //starboard/shared/gles/system_gles2.cc. If rdk-rpi is still a supported target, it likely requires the Raspberry Pi-specific GLES/EGL initialization that was previously in //starboard/raspi/shared/system_gles2.cc. If so, that file should be copied/moved to the rdk directory (e.g., starboard/contrib/rdk/shared/system_gles2_rpi.cc) and referenced here, rather than completely removing the override. If rdk-rpi is no longer supported, the target itself should be cleaned up.