Remove OpenCV version check

[Gold856]

Description

What changed?

The OpenCV version check historically used to detect incorrect OpenCV libraries has been removed.

Why?

This code and the issue it mitigated is impossible to hit by construction (at least in non-betas due to the OpenCV version being stable, however, if the OpenCV version changes during beta for some reason, you can still hit this), due to there being only one, year versioned Maven OpenCV artifact. There are no longer separate Maven artifacts per year (the year is no longer part of the group ID). This means given multiple dependencies that declare a dependency on OpenCV with differing versions, Gradle will always upgrade OpenCV to the latest version, which should typically be from GradleRIO.

Testing

• I have tested this change locally
• Test evidence (screenshots, videos, or test results):

OpenCV 2027-4.13.0-1 manually specified in build.gradle, upgraded to 2027-4.13.0-4 (from GradleRIO).

---

AI Disclosure

• This PR was authored entirely by me
• This PR includes AI-generated code (e.g., from GitHub Copilot, ChatGPT)
  • If yes, I have reviewed all AI-generated code for correctness
  • If yes, please describe which parts were AI-assisted:

Merge Checklist

• PR title is a short, imperative summary of changes
• PR description documents the what and why

Additional Checks (if applicable)

• User-facing changes? User documentation is updated
• Breaking changes? Migration guide is included in description
• Bug fix? Regression test is added
• New dependency? License compatibility is verified and steps have been taken to follow it
• Serde changes? All messages are regenerated with no unexpected hash changes
• Configuration changes? Changes are backwards compatible with previous season's last release
• Pipeline/data exchange changes? Frontend types are updated in ./photon-client/src/types

[mcm001]

at least in non-betas due to the OpenCV version being stable, however, if the OpenCV version changes during beta for some reason, you can still hit this

Implies that there isn't any process or guarantees upstream about stability (only from a nominal conops perspective), and that there is still value in this check during beta periods

dismissing to avoid an accidental merge

[Gold856]

Due to the timing of OpenCV releases, we are almost guaranteed to not hit that scenario. OpenCV releases every 6 months; right now, it's one release in winter (around December) and one for the summer (around June or July). December is way too late for us to integrate in time for kickoff; so historically, it's the summer release that's been deployed. It's more dependent on OpenCV's schedule than anything.