Remove code coverage from STS (#1537)

* WIP removal of code coverage

* more coverage removed

* more fixes

* fix tests

README.md

@@ -1,6 +1,4 @@
 [![Travis CI](https://travis-ci.org/Microsoft/sqltoolsservice.svg?branch=dev)](https://travis-ci.org/Microsoft/sqltoolsservice)
-[![AppVeyor](https://ci.appveyor.com/api/projects/status/github/Microsoft/sqltoolsservice?svg=true&retina=true&branch=dev)](https://ci.appveyor.com/project/kburtram/sqltoolsservice)
-[![Coverage Status](https://coveralls.io/repos/github/Microsoft/sqltoolsservice/badge.svg?branch=main)](https://coveralls.io/github/Microsoft/sqltoolsservice?branch=main)
 
 # Microsoft SQL Tools Service 
 The SQL Tools Service is an application that provides core functionality for various SQL Server tools.  These features include the following:
@@ -32,7 +30,6 @@ so that we can ensure we are solving the right problems in the right way.
 - File a bug or feature request as an [issue](https://github.com/Microsoft/sqltoolsservice/issues)
 - Comment on existing issues to give your feedback on how they should be fixed/implemented
 - Contribute a bug fix or feature implementation by submitting a pull request
-- Contribute more unit tests for feature areas that lack good coverage
 - Review the pull requests that others submit to ensure they follow [established guidelines]
   (#pull-request-guidelines)
 
@@ -44,7 +41,7 @@ Here's a high level list of guidelines to follow to ensure your code contributio
 - Follow established guidelines for commit hygiene
 - Write unit tests to validate new features and bug fixes
 - Ensure that the 'Release' build and unit tests pass locally
-- Ensure that the AppVeyor build passes for your change
+
 - Respond to all review feedback and final commit cleanup
 
 ### Practice Good Commit Hygiene
@@ -147,8 +144,7 @@ on this check so that our project will always have good generated documentation.
 
 - **The build and unit tests must run green**
 
-  Run all unit tests and code coverage tests to ensure all tests are passing and code coverage numbers
-  and not negatively impacted by your change.
+  Run all unit tests to ensure all tests are passing and are not negatively impacted by your change.
 
 - **Respond to code review feedback**