AdiGyro and AdiServo Device Support

[Tropix126]

What's the motivation for this feature?

Both of these devices are ones i've been avoiding for a while for various reasons, but we need to support them at some point.

Describe the solution you'd like

• Add an AdiGyro support for abstracting over the old 3-wire yaw-rate gyro.
• Add an AdiServo struct for controlling the legacy cortex-era servos.

Describe the drawbacks, if any

Both of these devices are very poorly documented in the SDK and may utilize private API functionality on VEXCode's side. Not sure.

• In AdiGyro's case, VEXCode has an is_calibrating function while PROS does not. There's no provided function in the SDK for this functionality, meaning it's probably some undocumented status bit. Fun.
• PROS also is forced into immediately calibrating the sensor as soon as vexDeviceAdiPortConfigSet is called.
• In AdiServo's case, PROS doesn't even support it at all. The units/range of the ADI setter is comlpetely unknown.

I also don't have access to any of this hardware to test on.