docs: fix all end of file newlines

Note: Some files are autogenerated and I did not yet
go through each source of generation to fix it there.
Instead I adjusted the filter to only exclude those
such that we can fix things in steps.

Tools/astyle/check_newlines.sh

@@ -3,14 +3,14 @@
 return_value=0
 
 # Check if there are files checked in that don't end in a newline (POSIX requirement)
-git grep --cached -Il '' -- ':!docs/*' | xargs -L1 bash -c 'if test "$(tail -c 1 "$0")"; then echo "No new line at end of $0"; exit 1; fi'
+git grep --cached -Il '' -- ':!docs/public/' ':!docs/ko/' ':!docs/uk/' ':!docs/zh/' | xargs -L1 bash -c 'if test "$(tail -c 1 "$0")"; then echo "No new line at end of $0"; exit 1; fi'
 
 if [ $? -ne 0 ]; then
 	return_value=1
 fi
 
 # Check if there are files checked in that have duplicate newlines at the end (fail trailing whitespace checks)
-git grep --cached -Il '' -- ':!docs/*' | xargs -L1 bash -c 'if tail -c 2 "$0" | ( read x && read y && [ x"$x" = x ] && [ x"$y" = x ]); then echo "Multiple newlines at the end of $0"; exit 1; fi'
+git grep --cached -Il '' -- ':!docs/public/' ':!docs/ko/' ':!docs/uk/' ':!docs/zh/' | xargs -L1 bash -c 'if tail -c 2 "$0" | ( read x && read y && [ x"$x" = x ] && [ x"$y" = x ]); then echo "Multiple newlines at the end of $0"; exit 1; fi'
 
 if [ $? -ne 0 ]; then
 	return_value=1

docs/assets/flight_log_analysis/plot_juggler/plotjuggler_sample_view.xml

@@ -88,4 +88,3 @@
  <snippets/>
  <!-- - - - - - - - - - - - - - - -->
 </root>
-

docs/assets/flight_log_analysis/plot_juggler/sample_log_boat_testing_layout.xml

@@ -132,4 +132,3 @@ function quaternionToYaw(x, y, z, w)
  </snippets>
  <!-- - - - - - - - - - - - - - - -->
 </root>
-

docs/book.json

@@ -105,4 +105,3 @@
     }
 
 }
-

docs/en/advanced_config/parameter_reference.md

@@ -40437,4 +40437,3 @@ Skip the controller.
 Reboot | minValue | maxValue | increment | default | unit
 --- | --- | --- | --- | --- | ---
   |  |  |  | 0 |
-

docs/en/airframes/airframe_reference.md

@@ -797,4 +797,3 @@ div.frame_variant td, div.frame_variant th {
 </tbody>
 </table>
 </div>
-

docs/en/config/safety_simulation.md

@@ -30,4 +30,3 @@ make run_failsafe_web_server
 <script setup>
 import { withBase } from 'vitepress';
 </script>
-

docs/en/flight_controller/ark_fpv.md

@@ -86,5 +86,3 @@ See the documentation [Ark Electronics GitBook](https://arkelectron.gitbook.io/a
 ## Pinout
 
 See the [DS-10 Pixhawk Autopilot Bus Standard](https://arkelectron.gitbook.io/ark-documentation/flight-controllers/ark-fpv/pinout)
-
-

docs/en/flight_modes_mc/index.md

@@ -54,4 +54,3 @@ Select the mode-specific sidebar topics for more detailed technical information.
 - [Flight Modes (Fixed-Wing)](../flight_modes_fw/index.md)
 - [Flight Modes (VTOL)](../flight_modes_vtol/index.md)
 - [Drive Modes (Rover)](../flight_modes_rover/index.md)
-

docs/en/flight_modes_vtol/offboard.md

@@ -1,4 +1,3 @@
 <Redirect to="../flight_modes/offboard" />
 
 # Offboard Mode (VTOL)
-

docs/en/frames_vtol/vtol_quadplane_fun_cub_vtol_pixhawk.md

@@ -82,4 +82,3 @@ After you finish calibration the VTOL is ready to fly.
 ## Support
 
 If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
-

docs/en/frames_vtol/vtol_quadplane_volantex_ranger_ex_pixhawk.md

@@ -122,4 +122,3 @@ Configure the frame as shown in QGroundControl below (do not forget to click **A
 ## Support
 
 If you have any questions regarding your VTOL conversion or configuration please visit <https://discuss.px4.io/c/px4/vtol>.
-

docs/en/getting_started/flight_controller_selection.md

@@ -39,4 +39,3 @@ Similarly, PX4 can also run natively Raspberry Pi (this approach is not generall
 PX4 is available on many popular commercial drone products, including some that ship with PX4 and others that can be updated with PX4 (allowing you to add mission planning and other PX4 Flight modes to your vehicle).
 
 For more information see [Complete Vehicles](../complete_vehicles/index.md).
-

docs/en/mavlink/streaming_messages.md

@@ -254,4 +254,3 @@ In order to avoid clogging communications links with messages that aren't needed
 
 If you needed, a GCS or other MAVLink API can request that particular messages are streamed at a particular rate using [MAV_CMD_SET_MESSAGE_INTERVAL](https://mavlink.io/en/messages/common.html#MAV_CMD_SET_MESSAGE_INTERVAL).
 A particular message can be requested just once using [MAV_CMD_REQUEST_MESSAGE](https://mavlink.io/en/messages/common.html#MAV_CMD_REQUEST_MESSAGE).
-

docs/en/middleware/uorb_graph.md

@@ -29,4 +29,3 @@ The graph has the following properties:
   You can also zoom the image.
 - The *Preset* selection list allows you to refine the list of modules that are shown.
 - The *Search* box can be used to find particular modules/topics (topics that are not selected by the search are greyed-out).
-

docs/en/modules/module_template.md

@@ -64,4 +64,3 @@ The template demonstrates the following additional features/aspects that are req
   documented [in the source code](https://github.com/PX4/PX4-Autopilot/blob/v1.8.0/src/platforms/px4_module.h#L381)):
   - They are used to print the command-line usage when entering `module help` on the console.
   - They are automatically extracted via script to generate the [Modules & Commands Reference](../modules/modules_main.md) page.
-

docs/en/msg_docs/index.md

@@ -300,5 +300,3 @@ NaN means the state was not controlled
 - [AirspeedValidatedV0](AirspeedValidatedV0.md)
 - [VehicleAttitudeSetpointV0](VehicleAttitudeSetpointV0.md)
 - [VehicleStatusV0](VehicleStatusV0.md) — Encodes the system state of the vehicle published by commander
-
-    

docs/en/peripherals/mavlink_peripherals.md

@@ -120,4 +120,3 @@ Links to setup instructions for specific MAVLink components:
 - [Serial Port Configuration](../peripherals/serial_configuration.md)
 - [PX4 Ethernet Setup > PX4 MAVLink Serial Port Configuration](../advanced_config/ethernet_setup.md#px4-mavlink-serial-port-configuration)
 - [Serial Port Mapping](../hardware/serial_port_mapping.md)
-

docs/scripts/gen_sitemap.py

@@ -129,4 +129,3 @@ print("Sitemap generated to: %s" % outputfile)
 
 #print("BRANCH_NAME: %s" % BRANCH_NAME)
 #print("Build version: %s" % build_version)
-