Schema fetch failures when systems proxy protection requires SSL

[Michael-Macal]

Network traffic protected by the preferred secure ONLY (https only) security settings will not be able to fetch the eslintrc schema.

see https://www.blog.google/products/chrome/milestone-chrome-security-marking-http-not-secure/

Suggested fix: update jsonValidation urls from http to https

existing entries in package.json

		"jsonValidation": [
			{
				"fileMatch": ".eslintrc",
				"url": "http://json.schemastore.org/eslintrc"
			},
			{
				"fileMatch": ".eslintrc.json",
				"url": "http://json.schemastore.org/eslintrc"
			},
			{
				"fileMatch": "package.json",
				"url": "./package-json-schema.json"
			}
		],

suggested change:

		"jsonValidation": [
			{
				"fileMatch": ".eslintrc",
				"url": "https://json.schemastore.org/eslintrc"
			},
			{
				"fileMatch": ".eslintrc.json",
				"url": "https://json.schemastore.org/eslintrc"
			},
			{
				"fileMatch": "package.json",
				"url": "./package-json-schema.json"
			}
		],

[dbaeumer]

Makes sense. Will make the change.

[dbaeumer]

This got addressed a while back.