Allow configuring maximum target count

[2826WaveRobotics]

Description

We wanted to track more than 10 objects in an Object Detection pipeline, so we added a "Maximum Targets" setting for when "Show Multiple Targets" is enabled. The default value is 10, so no existing configuration should change, though a "Show multiple targets" setting is redundant in theory.

None of the documentation mentioned this 10-object limit, so nothing there changed for now.

Meta

Merge checklist:

• Pull Request title is short, imperative summary of proposed changes
• The description documents the what and why
• If this PR changes behavior or adds a feature, user documentation is updated
• If this PR touches photon-serde, all messages have been regenerated and hashes have not changed unexpectedly
• If this PR touches configuration, this is backwards compatible with settings back to v2025.3.2
• If this PR touches pipeline settings or anything related to data exchange, the frontend typing is updated
• If this PR addresses a bug, a regression test for it is added

[samfreund]

Prefer increasing the hardcoded value to a sane number given the current game. We'd like to avoid adding additional sliders that can be avoided. If you're willing to add docs for the limit, go for it, but don't feel obliged.

[2826WaveRobotics]

Understandable. What are your thoughts on entirely switching "Show Multiple Targets" to a "Maximum Targets" slider, given its current purpose isn't entirely clear and can be made more versatile as a configurable value? My understanding is that the existing limit is temporary, and I see use cases where teams want to track more than 50 targets to calculate a distribution of game pieces, since the current logic only returns the 50 largest in view.

[samfreund]

Understandable. What are your thoughts on entirely switching "Show Multiple Targets" to a "Maximum Targets" slider, given its current purpose isn't entirely clear and can be made more versatile as a configurable value? My understanding is that the existing limit is temporary, and I see use cases where teams want to track more than 50 targets to calculate a distribution of game pieces, since the current logic only returns the 50 largest in view.

I think that sounds like a reasonable solution. This way, we don't add a new slider (our main concern being clutter and slider overload). The one note is that the max value should be set to 127, as that's the maximum PhotonVision's serialization can support.