Rename excludedHosts -> allowedHosts in no-hardcoded-env-urls rule (breaking change)

"no-hardcoded-env-urls": {
"level": "warning",
"disallowedhosts": [
"gallery.azure.com",
"management.core.windows.net",
"management.azure.com",
"database.windows.net",
"core.windows.net",
"login.microsoftonline.com",
"graph.windows.net",
"trafficmanager.net",
"datalake.azure.net",
"azuredatalakestore.net",
"azuredatalakeanalytics.net",
"vault.azure.net",
"api.loganalytics.io",
"asazure.windows.net",
"region.asazure.windows.net",
"batch.core.windows.net"
],
"excludedhosts": [
"schema.management.azure.com"
]
}
}

excludedhosts doesn't make a lot of sense - seems like a synonym of disallowedHosts. allowedHosts would be much clearer. It is a breaking change but unlikely anyone is using it.

Start by locating the no-hardcoded-env-urls rule and its excludedhosts configuration. Rename that option to allowedHosts, then check the rule's configuration coverage and update any references so the new name is consistently recognized.

Written by the indexing model from the issue text.