Missionitem: Set condition_yaw default to absolute heading (#10594)

My experience is that I change heading to absolute direction, rather
than relative (because relative will accumulate any heading error on
incomplete yaw, especially if the command is executed while turning.)
The absolute heading is the most used/typical way of using this mission
item. This change does not affect missions that are already created,
only the default selection while creating a mission.
The default yaw rate is also very slow (unchanged) meaning that any
relative yaw command will result in an unknown result, unlress performed
long since last one relative.
Final reason: Scanning missions consists of with many waypoints are
always at an absolute heading. While "make a panoramic turn" with
relative amont of degrees, are usually single-command. So it is better
to default to a setting used for missions with many such commands.

Co-authored-by: forced_to_this_mess <eudhe@deed.no>

src/MissionManager/MavCmdInfoCommon.json

@@ -457,7 +457,7 @@
                 "label":            "Offset",
                 "enumStrings":      "Relative,Absolute",
                 "enumValues":       "1,0",
-                "default":          1
+                "default":          0
             }
         },
         { "id": 176, "rawName": "MAV_CMD_DO_SET_MODE", "friendlyName": "Set mode" },