Remove old Run_uncrustify_for_sources.{bat,sh}

Remove the old scripts to run uncrustify on its own sources. The new
runner makes these unnecessary.

.travis.yml

@@ -141,8 +141,6 @@ script:
   - if [ "x${BUILD_TYPE}" != "xcross" ]; then ../scripts/run_ctest.py; fi
   # collect coverage (needs to be after running tests)
   - if [ "x${BUILD_TYPE}" == "xcoverage" ]; then make coverage; fi
-  # test if all the sources are conform to the forUncrustifySources.cfg config file
-  - if [ "x${BUILD_TYPE}" == "xrelease" ]; then cd ../ && ./scripts/Run_uncrustify_for_sources.sh; cd -; fi
 
   # DO NOT REMOVE (debugging purposes)
   #- /home/travis/build/uncrustify/uncrustify/build/uncrustify -l cs -c /home/travis/build/uncrustify/uncrustify/tests/config/U10-Cpp.cfg -f /home/travis/build/uncrustify/uncrustify/tests/input/cs/newlines.mm -L A

CONTRIBUTING.md

@@ -31,6 +31,6 @@ There are lots of ways to contribute to Uncrustify:
     - The change should always be accompanied by regression tests (explain why if not possible)
 * Preparing a Pull Request (PR):
     - To reduce the likelihood of conflicts and test failures, try to avoid merges, rebasing your work on top of latest master before creating a PR 
-    - Verify that your code is properly formatted by running `scripts/Run_uncrustify_for_sources`
+    - Verify that your code is working properly by running `ctest` in your build directory
     - The PR title should represent _what_ is being changed (a rephrasing of the branch name if set correctly)
     - The PR description should document the _why_ the change needed to be done and _not how_ which should be obvious by doing the code review