pre-commit trailing whitespace auto clean up (#12841)

Author: jbampton

.pre-commit-config.yaml

@@ -162,7 +162,7 @@ repos:
       - id: forbid-submodules
       - id: mixed-line-ending
       - id: trailing-whitespace
-        files: ^(LICENSE|NOTICE)$|\.(bat|cfg|cs|css|gitignore|header|in|install|java|md|properties|py|rb|rc|sh|sql|te|template|txt|ucls|vue|xml|xsl|yaml|yml)$|^cloud-cli/bindir/cloud-tool$|^debian/changelog$
+        files: ^(LICENSE|NOTICE)$|README$|\.(bat|cfg|config|cs|css|erb|gitignore|header|in|install|java|md|properties|py|rb|rc|sh|sql|svg|te|template|txt|ucls|vue|xml|xsl|yaml|yml)$|^cloud-cli/bindir/cloud-tool$|^debian/changelog$
         args: [--markdown-linebreak-ext=md]
         exclude: ^services/console-proxy/rdpconsole/src/test/doc/freerdp-debug-log\.txt$
   - repo: https://github.com/codespell-project/codespell
@@ -186,7 +186,7 @@ repos:
         description: check Markdown files with markdownlint
         args: [--config=.github/linters/.markdown-lint.yml]
         types: [markdown]
-        files: \.(md|mdown|markdown)$
+        files: \.md$
   - repo: https://github.com/adrienverge/yamllint
     rev: v1.37.1
     hooks:

plugins/hypervisors/hyperv/DotNet/ServerResource/AgentShell/App.config

@@ -35,7 +35,7 @@
       <appender-ref ref="EventLogAppender"/>
     </root>
   </log4net>
-  
+
   <applicationSettings>
     <CloudStack.Plugin.AgentShell.AgentSettings>
       <setting name="cpus" serializeAs="String">

plugins/hypervisors/hyperv/DotNet/ServerResource/HypervResource/App.config

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8" ?>
-<!-- 
+<!--
     Note: Add entries to the App.config file for configuration settings
     that apply only to the Test project.
 -->

plugins/hypervisors/hyperv/DotNet/ServerResource/ServerResource.Tests/App.config

@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- 
+<!--
     Note: Add entries to the App.config file for configuration settings
     that apply only to the Test project.
 -->

tools/devcloud4/binary-installation-advanced/marvin.cfg.erb

@@ -5,9 +5,9 @@
 #  to you under the Apache License, Version 2.0 (the
 #  "License"); you may not use this file except in compliance
 #  with the License.  You may obtain a copy of the License at
-#  
+#
 #    http://www.apache.org/licenses/LICENSE-2.0
-#  
+#
 #  Unless required by applicable law or agreed to in writing,
 #  software distributed under the License is distributed on an
 #  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

tools/devcloud4/binary-installation-basic/marvin.cfg.erb

@@ -5,9 +5,9 @@
 #  to you under the Apache License, Version 2.0 (the
 #  "License"); you may not use this file except in compliance
 #  with the License.  You may obtain a copy of the License at
-#  
+#
 #    http://www.apache.org/licenses/LICENSE-2.0
-#  
+#
 #  Unless required by applicable law or agreed to in writing,
 #  software distributed under the License is distributed on an
 #  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY

tools/utils/database_comparision_during_upgrade/README

@@ -15,14 +15,14 @@ What this tool is capable to do is
 
 The usage is as follows
 1.	First run fresh_install_data_collection.sh file to generate data from fresh install setup .
-	This will be used for comparing between fresh install and upgrade setup. 
+	This will be used for comparing between fresh install and upgrade setup.
 	This is a onetime activity and need to be repeated only when there is some DB changes for that release .
-	Output of this script will come in a base_data folder 
+	Output of this script will come in a base_data folder
 
 2.	Just before upgrade you need to run before_upgrade_data_collection.sh  file to collect required data needed to compare before upgrade and after upgrade setup data
 	The output of this script will come in folder data_before_upgrade
 
-3.	After upgrade  run cloud_schema_comparision.sh to compare cloud database all tables schema between fresh and upgraded setup. 
+3.	After upgrade  run cloud_schema_comparision.sh to compare cloud database all tables schema between fresh and upgraded setup.
 	NOTE: this script requires step 1 output in current working directory
 
 4.	After upgrade  run usage_schema_comparision.sh to compare cloud usage all tables schema between fresh and upgraded setup
@@ -41,4 +41,4 @@ The usage is as follows
 	•	Database user
 	•	Database user password
 
-8.	Result will be shown in the form of files . 
+8.	Result will be shown in the form of files .