chore: Reformat miscellaneous files

Remove trailing whitespace and ensure files end with newlines.

Author: kjarosh

.gitattributes

@@ -14,5 +14,5 @@
 *.swf  binary
 *.swc  binary
 
-# Fix GH saying Ruffle is written in ActionScript 
+# Fix GH saying Ruffle is written in ActionScript
 tests/tests/swfs/** linguist-vendored

desktop/assets/Assets.xcassets/RuffleBlue.colorset/Contents.json

@@ -18,4 +18,4 @@
             }
         }
     ]
-}
+}

desktop/assets/Assets.xcassets/RuffleOrange.colorset/Contents.json

@@ -18,4 +18,4 @@
             }
         }
     ]
-}
+}

desktop/assets/OpenH264-license.txt

@@ -2,13 +2,13 @@
 About The Cisco-Provided Binary of OpenH264 Video Codec
 -------------------------------------------------------
 
-Cisco provides this program under the terms of the BSD license.  
+Cisco provides this program under the terms of the BSD license.
 
-Additionally, this binary is licensed under Cisco’s AVC/H.264 Patent Portfolio License from MPEG LA, at no cost to you, provided that the requirements and conditions shown below in the AVC/H.264 Patent Portfolio sections are met.  
+Additionally, this binary is licensed under Cisco’s AVC/H.264 Patent Portfolio License from MPEG LA, at no cost to you, provided that the requirements and conditions shown below in the AVC/H.264 Patent Portfolio sections are met.
 
-As with all AVC/H.264 codecs, you may also obtain your own patent license from MPEG LA or from the individual patent owners, or proceed at your own risk.  Your rights from Cisco under the BSD license are not affected by this choice.  
+As with all AVC/H.264 codecs, you may also obtain your own patent license from MPEG LA or from the individual patent owners, or proceed at your own risk.  Your rights from Cisco under the BSD license are not affected by this choice.
 
-For more information on the OpenH264 binary licensing, please see the OpenH264 FAQ found at http://www.openh264.org/faq.html#binary 
+For more information on the OpenH264 binary licensing, please see the OpenH264 FAQ found at http://www.openh264.org/faq.html#binary
 
 A corresponding source code to this binary program is available under the same BSD terms, which can be found at http://www.openh264.org
 
@@ -32,7 +32,7 @@ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS”
 AVC/H.264 Patent Portfolio License Notice
 -----------------------------------------
 
-The binary form of this Software is distributed by Cisco under the AVC/H.264 Patent Portfolio License from MPEG LA, and is subject to the following requirements, which may or may not be applicable to your use of this software: 
+The binary form of this Software is distributed by Cisco under the AVC/H.264 Patent Portfolio License from MPEG LA, and is subject to the following requirements, which may or may not be applicable to your use of this software:
 
 THIS PRODUCT IS LICENSED UNDER THE AVC PATENT PORTFOLIO LICENSE FOR THE PERSONAL USE OF A CONSUMER OR OTHER USES IN WHICH IT DOES NOT RECEIVE REMUNERATION TO (i) ENCODE VIDEO IN COMPLIANCE WITH THE AVC STANDARD (“AVC VIDEO”) AND/OR (ii) DECODE AVC VIDEO THAT WAS ENCODED BY A CONSUMER ENGAGED IN A PERSONAL ACTIVITY AND/OR WAS OBTAINED FROM A VIDEO PROVIDER LICENSED TO PROVIDE AVC VIDEO.  NO LICENSE IS GRANTED OR SHALL BE IMPLIED FOR ANY OTHER USE.  ADDITIONAL INFORMATION MAY BE OBTAINED FROM MPEG LA, L.L.C. SEE HTTP://WWW.MPEGLA.COM
 
@@ -52,8 +52,8 @@ In addition, the Cisco-provided binary of this Software is licensed under Cisco'
 
        "OpenH264 Video Codec provided by Cisco Systems, Inc."
 
-4.  Any third-party software that makes use of the Cisco-provided binary must reproduce all of the above text, as well as this last condition, in the EULA and/or in another location where licensing information is to be presented to the end user.  
- 
+4.  Any third-party software that makes use of the Cisco-provided binary must reproduce all of the above text, as well as this last condition, in the EULA and/or in another location where licensing information is to be presented to the end user.
+
 
 
                           v1.0

desktop/assets/macOSEntitlements.plist

@@ -8,4 +8,4 @@
         <key>com.apple.security.network.client</key>
         <true/>
     </dict>
-</plist>
+</plist>

desktop/packages/windows/wix/ruffle.wxs

@@ -2,9 +2,9 @@
 
 <!--
     wix extension add -g WixToolset.UI.wixext
-    wix extension add -g WixToolset.Util.wixext 
+    wix extension add -g WixToolset.Util.wixext
     RUFFLE_VERSION="xxxxxx" wix build ruffle.wxs -ext WixToolset.UI.wixext -ext WixToolset.Util.wixext -arch x64
-    -->
+-->
 
 <Wix xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ui="http://wixtoolset.org/schemas/v4/wxs/ui"
      xmlns:util="http://wixtoolset.org/schemas/v4/wxs/util"
@@ -93,11 +93,11 @@ http://wixtoolset.org/schemas/v4/wxs/util https://raw.githubusercontent.com/wixt
         </StandardDirectory>
 
         <Component Id='Associations' Guid='2216512a-9c76-412f-ba36-08e703a56f25'>
-            <!-- 
+            <!--
                 This creates the Ruffle progids and *hints* that Ruffle can be associated with them.
-                This may or may not cause Windows to make the association, but more likely makes it ask the user 
+                This may or may not cause Windows to make the association, but more likely makes it ask the user
                 what they want the next time they open a swf.
-                -->
+            -->
 
             <ProgId Id='Ruffle.swf' Description='Flash Movie' Icon="DesktopEXE" IconIndex="1">
                 <Extension Id='swf' ContentType='application/x-shockwave-flash'>
@@ -124,7 +124,7 @@ http://wixtoolset.org/schemas/v4/wxs/util https://raw.githubusercontent.com/wixt
         <Component Id='ApplicationInfo' Guid='f7e7c5bb-729c-427e-b913-fd0d2e11a143'>
             <!--
                 Tell windows a few properties about our application, so that it can handle it slightly better in "Open With"
-                
+
                 (wondering how Windows matches these to the ruffle.exe that we install at some arbitrary path the user picks?)
                 (well that's the fun part... it doesn't! Windows SOLELY goes by the filename. Isn't that convenient?!)
                 (rename an executable and suddenly windows can't associate these things with it anymore whoops)

rustfmt.toml

@@ -1 +1 @@
-newline_style = "Unix"
+newline_style = "Unix"

stub-report/generate-report.sh

@@ -10,4 +10,4 @@ mkdir /tmp/ruffle-website-update
 cargo run --locked --package stub-report /tmp/ruffle-website-update/implementation.json
 
 git clone https://github.com/ruffle-rs/api-report /tmp/ruffle-website-update/api-report
-cargo run --manifest-path /tmp/ruffle-website-update/api-report/Cargo.toml  -- -s /tmp/ruffle-website-update/api-report/avm2_specification.json -i /tmp/ruffle-website-update/implementation.json -o avm2_report.json
+cargo run --manifest-path /tmp/ruffle-website-update/api-report/Cargo.toml  -- -s /tmp/ruffle-website-update/api-report/avm2_specification.json -i /tmp/ruffle-website-update/implementation.json -o avm2_report.json

tests/mocket/Cargo.toml

@@ -15,4 +15,4 @@ anyhow = { workspace = true }
 clap = { workspace = true }
 tracing = { workspace = true}
 tracing-subscriber = { workspace = true }
-ruffle_socket_format = { path = "../socket-format" }
+ruffle_socket_format = { path = "../socket-format" }