trivial: Prefer HTTPS over HTTP for various links

Signed-off-by: Jan Keromnes <jan.keromnes@typefox.io>

.vscode/extensions.json

@@ -1,5 +1,5 @@
 {
-  // See http://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
+  // See https://go.microsoft.com/fwlink/?LinkId=827846 to learn about workspace recommendations.
   // Extension identifier format: ${publisher}.${name}. Example: vscode.csharp
   // List of extensions which should be recommended for users of this workspace.
   "recommendations": [

CODE_OF_CONDUCT.md

@@ -49,7 +49,7 @@ Project maintainers who do not follow or enforce the Code of Conduct in good fai
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant](http://contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
 For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq
 

CONTRIBUTING.md

@@ -55,7 +55,7 @@ We follow the coding guidelines described
 Before your contribution can be accepted by the project team contributors must
 electronically sign the Eclipse Contributor Agreement (ECA).
 
-* http://www.eclipse.org/legal/ECA.php
+* https://www.eclipse.org/legal/ECA.php
 
 Commits that are provided by non-committers must have a Signed-off-by field in
 the footer indicating that the author is aware of the terms by which the
@@ -72,7 +72,7 @@ The sign-off is a simple line at the end of the explanation for the patch. Your
 signature certifies that you wrote the patch or otherwise have the right to
 pass it on as an open-source patch. The rules are pretty simple: if you can
 certify the below (from
-[developercertificate.org](http://developercertificate.org/)):
+[developercertificate.org](https://developercertificate.org/)):
 
 ```
 Developer Certificate of Origin

LICENSE

@@ -1,6 +1,6 @@
 This program and the accompanying materials are made available under the
 terms of the Eclipse Public License v. 2.0 which is available at
-http://www.eclipse.org/legal/epl-2.0, or GNU General Public License, version 2
+https://www.eclipse.org/legal/epl-2.0, or GNU General Public License, version 2
 with the GNU Classpath Exception which is available at https://www.gnu.org/software/classpath/license.html.
 
 # Eclipse Public License - v 2.0

NOTICE.md

@@ -18,7 +18,7 @@ source code repository logs.
 
 This program and the accompanying materials are made available under the terms
 of the Eclipse Public License v. 2.0 which is available at
-http://www.eclipse.org/legal/epl-2.0. This Source Code may also be made
+https://www.eclipse.org/legal/epl-2.0. This Source Code may also be made
 available under the following Secondary Licenses when the conditions for such
 availability set forth in the Eclipse Public License v. 2.0 are satisfied: GNU
 General Public License, version 2 with the GNU Classpath Exception which is

doc/Developing.md

@@ -112,9 +112,9 @@ Start your browser on https://localhost:3000.
 
 ### Run the browser example with Gitpod
 
-[Gitpod](http://gitpod.io/) is a Theia-based IDE for GitHub.
+[Gitpod](https://www.gitpod.io/) is a Theia-based IDE for GitHub.
 You can start by prefixing any GitHub URL in the Theia repository with `gitpod.io/#`:
-- Open http://gitpod.io/#https://github.com/eclipse-theia/theia to start development with the master branch.
+- Open https://gitpod.io/#https://github.com/eclipse-theia/theia to start development with the master branch.
 - Gitpod will start a properly configured for Theia development workspace, clone and build the Theia repository.
 - After the build is finished, run from the terminal in Gitpod: