Link Protection Improvements

[octref]

• Allow adding trusted domains Allow adding trusted domains #80010
• Link protection ux is confusing Link protection ux is confusing #80489
• Link protection UI inconsistency Link protection UI inconsistency #79900
• Add a setting for disabling link protection Add a setting for disabling link protection #80592
• Reset trusted domains list for link protection Reset trusted domains list for link protection #80333

[octref]

The new dialog is more clearer:

And the configuration process becomes editing a JSON file (for the 3rd option above):

These two commands will be available:

[octref]

@jrieken In Redmond we discussed how we can improve the link protection configuring experience, but we realize QuickInput is not the right widget for all CRUD operations. So I went with the approach of having a FS provider and let use configure the JSON setting.

I see #10547 and @Tyriar is interested in having something similar for editing an in-memory item in terminal area. I'm wondering if we should have a dedicated schema for such use cases.

[aeschli]

@octref Why is the list of trusted domains done is a separate (virtual) resource and not part of the (user) settings?
That way it will be profit from our synced-settings story.

[aeschli]

Can you describe what is there to verify (I have the feeling this would even deserve it's own test item...)

[Tyriar]

@aeschli because an extension could just write the settings and bypass the security feature completely.

[samrat-gavale]

@octref how is this to be handled in an enterprise scenario? e.g. like when an engineering services team wants to create a one-click setup for a development environment, which consists of a couple of extensions pointing users to a bunch of external sites? Currently there is no way but to ask each developer to configure those domains.

[octref]

@samrat-gavale I opened #82794 but I don't have a plan yet. If you have a good suggestion how this might work, please follow up in that thread.