UI changes to help new features move towards WebDriver BiDi

[alexnj]

WebDriver BiDi is geared towards more new features be incubated and tested in a more cross-browser compatible way vs. adding classic WebDriver endpoints. This feature request is to track UI changes to add BiDi checkpoints in Intent to Prototype and Debuggability review gates.

Describe the solution you'd like

1. ChromeStatus Feature UI changes to add an "Automation spec" checkbox in the API spec section, with associated description. Rough mock below:

Description text: The spec document has sufficient automation via WebDriver BiDi protocol including proper CDDL types.

2. Same/similar question in the Debuggability gate template for Intent-to-Ship, for reviewers to consider while evaluating an intent to ship request.

Additional context

• WebDriver BiDi automation spec examples: https://www.w3.org/TR/permissions/#automation and https://webbluetoothcg.github.io/web-bluetooth/#automated-testing
• CDDL example: https://www.w3.org/TR/permissions/#webdriver-bidi-command-permissions-setPermission,

[alexnj]

cc @past @sadym-chromium

[itsAyush5]

Can u assign me this issue @alexnj