extensions.allowed setting should support an indirection

[isidorn]

extensions.allowed setting is currently controlled via group policy by enterprise admins. The downside of that is that this setting can be pretty dynamic, and enterprises want to change the value every week (or more often). What we hear from enterprises is that changing a value of a group policy is a heavy process, and ideally they would not change the value of extensions.allowed any time they want to update the list of allowed extensions.

To work-around this I suggest that extensions.allowed supports also setting a string - which would mean a location of the json file which has the allowed list of extensions. The location could be local or url?

[skofman1]

@isidorn , @sandy081 , any chance you can work on this for the Nov release?

[isidorn]

I just discussed with Sandeep, and we will try to put this on the November plan. Thus it will be in VS Code stable start of December. Sandeep - I will optimistically assign this to November milestone.

I know we originally discussed start of November - but due to GH universe a lot of our prioritization has changed.