🐛 Docs incorrectly state optical sensor methods aren't available

[NoahK216]

Referring to purduesigbots/pros#624

Describe the bug
Certain methods on the optical sensor (such as optical_get_hue, optical_get_saturation, optical_get_brightness, optical_get_proximity) claim that the methods are "not available" while gesture detection mode is enabled (interestingly, they never describe what's returned by these functions if the methods are called in this state).

optical_get_saturation:

This is not available if gestures are being detected. Saturation has a range of 0 to 1.0

However, from testing on physical hardware, this claim seems to be incorrect. All RGBC-related functions work fine, even when gestures are being detected. My test procedure is outlined here.

To Reproduce

pros::Optical sensor(1);
sensor.enable_gesture(); // Gesture detection is now enabled.
printf("%lf\n", sensor.get_hue()); // Should work fine

Expected behavior
Docs should not claim that these methods are inaccessible, and elaborate further on gesture detection mode.

• It's currently unclear to me why there's actually a toggle for gesture detection in the first place, actually. If everything works with it enabled, then what's the harm keeping it on always? Does having it enabled degrade the sensor's RGBC readings? Is it a measure to save on power consumption? There's no way to know, and I haven't been able to find a concrete answer regarding this anywhere.

Screenshots

Desktop (please complete the following information):

• OS: Windows 11
• Version 23H2 (26020.1000)

Additional context
None

[SizzinSeal]

The API has been nuked so this is no longer an issue