radio_status: change 'fixed' field name to 'fix' so it does not clash with 'fixed' floating-point notation on the IDL generation

The user does not need to configure this, so we can hide it from the UI.

Clarify which  componets is on which index for the item array

At the moment it is only declared a component, PX4IO.

Instead of calling _updateSetpoints(), that also sets the thrust setpoint,
which is then overwritten again.

It's confusing and there is a corner case where the result is incorrect:
*= 0 will not set the variable to 0 if it's already NAN.

This fixes the build with Python 3.7.

The typhoon has a 6011_typhoon_h480.post script that got matched as well.
Now we exclude all files that contain a dot (apparently it's not so easy
to do generic pattern matching in a portable way, but this works).

    - sitl_gazebo in PX4/Firmware (6c34407d): https://github.com/PX4/sitl_gazebo/commit/9d512af0075659f0ace91ec0e2f8c8a170f911fb
    - sitl_gazebo current upstream: https://github.com/PX4/sitl_gazebo/commit/1264b74493cd2f362d852530bcc7423a013f2151
    - Changes: https://github.com/PX4/sitl_gazebo/compare/9d512af0075659f0ace91ec0e2f8c8a170f911fb...1264b74493cd2f362d852530bcc7423a013f2151

1264b74 2018-09-30 TSC21 - gazebo_motor_failure_plugin: clean up and fix for Gazebo 9
77141e7 2018-09-29 TSC21 - Travis: add naming for jobs within the build matrix
e46f82a 2018-09-29 TSC21 - add new 18.04 Melodic build
5b93919 2018-09-29 TSC21 - Travis: update ROS docker container

    - v2.0 in PX4/Firmware (f7a1da2261c579ef680c7d3b7a016bc4c6d13601): https://github.com/mavlink/c_library_v2/commit/e5f6257dd005b6fb3bff23d45f2b3b417b52539b
    - v2.0 current upstream: https://github.com/mavlink/c_library_v2/commit/c5b465f5b455c5e6116cc5b6bf1332747a7b7494
    - Changes: https://github.com/mavlink/c_library_v2/compare/e5f6257dd005b6fb3bff23d45f2b3b417b52539b...c5b465f5b455c5e6116cc5b6bf1332747a7b7494

    c5b465f 2018-10-01 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/bae3015ecc05299968362a4623d506ea2840ec86

board_get_px4_guid() called board_get_uuid() with a 2 bytes offset into an
uint8_t array. This gives no guarantees on alignment, and board_get_uuid()
casts it to an uint32_t array, leading to potentially unaligned accesses.

Just to make sure we never have an UUID == 0

   This file was clearly clearly but built.