[Feature]: Add an option to enable only text options in the default context menus

Describe the feature/enhancement you need

Currently, there exists an option called AreDefaultContextMenusEnabled which can be set to true or false to enable or disable default context menus in the WebView2. The problem is, often it is desirable to disable various in-built context menu options such as Save as, web capture, copy link, open in new window, etc. while still enabling text options such as Cut, Copy and Paste - in fact, this is the default behaviour of the Microsoft Edge based UWP WebView - it shows only text options in its context menus.

UWP WebView context menu with a link selected:

WebView2 context menu with a link selected:

The scenario/use case where you would use this feature

This would be useful as in many situations that require a web view, developers want to remove normal browsers items such as the option to open links in new windows, use web capture, etc. but still allow users to copy and paste text from the context menu like the UWP WebView. An example of this could be an in app help manual where these extra options do not make sense but the user may still want to copy text (for example, the user manual might have example input data for the app that the user may want to copy and past into the app). Microsoft's own Get Help app might find this feature useful as well as it disables the default WebView2 context menus but there is a search text box which currently has no context menu and as a user I think it would be beneficial to have a Cut, Copy Paste context menu for that text box.

How important is this request to you?

Nice to have. There are other ways to tackle this, but having official API support would be beneficial.

Suggested implementation

At the moment, it is possible to customise the default context menus using the items' names to identify them, however, as far as I know, there is no official documentation that describes the names of the default context menu items and so, as a developer, I am unsure if they might change in the future or if we should be using them. Additionally, since this is such a common scenario, I think it would be beneficial for this to be an option that can be opted into, as that would be much quicker than customising the menu manually. This could also help with migrating from the old UWP WebView, as, when enabled, it would match the context menu behaviour to that of the old UWP WebView. Also, on the topic of the names, see this issue: https://github.com/MicrosoftEdge/WebView2Feedback/issues/3297.

What does your app do? Is there a pending deadline for this request?

No response