Bounds checking could use improvement

[mduffor]

https://github.com/FRC5411/Lofty-2023/blob/89c03d89e93596035ac60450451b82608aee2649/src/main/java/frc/robot/subsystems/Arm.java#L171

Current code compares output values against themselves, which doesn't solve anything.
Bounds checking both high and low, forward and back, would be useful.
Bounds should be defined with constants, not using magic numbers.

[RDc12Programming]

the check against itself is actually a check for NaN, which would indicate a value outside or inside the reach of the arm. the x/y checks are to ensure we do not breach frame perimiter, and do need to me notated and moved to constants. will do

[mduffor]

It is much clearer to do output[0].isNan() or (Double.isFinite(output[0]) == false)