1ES Migration

- Change release links and status badge

README.md

@@ -1,6 +1,6 @@
 ## Build status
 
-[![Build status](https://dev.azure.com/ms/azure-pipelines-vscode/_apis/build/status/Langserv%20CI?branchName=main)](https://dev.azure.com/ms/azure-pipelines-vscode/_build/latest?definitionId=24?branchName=main)
+[![Build Status](https://dev.azure.com/mseng/PipelineTools/_apis/build/status%2Fazure-pipelines-language-server%2FLangserv%20CI?repoName=microsoft%2Fazure-pipelines-language-server&branchName=main)](https://dev.azure.com/mseng/PipelineTools/_build/latest?definitionId=17102&repoName=microsoft%2Fazure-pipelines-language-server&branchName=main)
 
 ## Features
 

RELEASE.md

@@ -21,5 +21,5 @@
     6. Publish this to npm. `npm publish azure-pipelines-language-server-0.1.2.tgz`
 6. Create a PR from your ship branch to `main`. Merge it. :tada: you're done!
 
-[release-service]: https://dev.azure.com/ms/azure-pipelines-vscode/_build?definitionId=33 "Language service release pipeline"
-[release-server]: https://dev.azure.com/ms/azure-pipelines-vscode/_build?definitionId=34 "Language server release pipeline"
+[release-service]: https://dev.azure.com/mseng/PipelineTools/_build?definitionId=17100 "Language service release pipeline"
+[release-server]: https://dev.azure.com/mseng/PipelineTools/_build?definitionId=17139 "Language server release pipeline"