Request-Data-Stream requests interfere with ROS/SLAM setup

APWeb seems to be sending [REQUEST_DATA_STREAM](https://mavlink.io/en/messages/common.html#REQUEST_DATA_STREAM) messages at about 10hz and within this message it requests the flight controller set all stream rates to 4hz. This interferes with the ROS/SLAM setups (described here on the wiki) that need much higher IMU data rates (like 50hz).

Note that I didn't actually need to be using the APWeb page for this issue to occur.

Of course I can disable APWeb on APSync (and add instructions on our wiki) but it would be nice if APWeb only requested these stream rates if it was getting data at a lower rate than 4hz.

Start by tracing APWeb's REQUEST_DATA_STREAM behavior and compare it with the ROS/SLAM rates described in the linked wiki. Done means APWeb does not force 4 Hz when higher-rate data is already available, while retaining the intended behavior when data is below 4 Hz; validate the result with APWeb enabled on APSync.

Written by the indexing model from the issue text.