Enforce parameter valid range

Currently the Min and Max values for parameters are only described in comment form, and are used by some GCS's for presentation of the data as a "slider" or similar, but they are NOT sanity checked in the flight-controller itself, making it high-risk that user/s can enter arbitrary incorrect information into their system.
Typically with "value less" data like P I and D values that have weird range/s ( such as 0.01 -> 0.001 ) etc are easy to misplace the decimal point, and this can be catastrophic to flight performance, and it's just a typo.

Start by examining how Min and Max parameter values are currently represented and consumed by the flight controller and ground control systems. Define the validation behavior and its handling of values outside the declared range, then verify that incorrect parameter values can no longer be accepted without breaking existing parameter use.

Written by the indexing model from the issue text.