feat: Imported Firefox 134 and Firefox 135 schema data

[rpl]

The updated schema data includes the following changes

Firefox 134:

• Bug 1924071 - Remove the purpose option from search URLs: removed unused API schema related to legacy application provided search engines
• Bug 1929104 - Disable SandboxProfiler* by default when profiling: added "sandbox" to the ProfilerFeature strings enum
• Bug 1919323 - Add support for optional-only permissions: introduced new OptionalOnlyPermission type
• Bug 1917799 - Implement a WebExtension experimental API for Firefox AI Platform: introduced new trialML optional only permission
• Bug 1903498 - Typo in schema file network_status.json: fixed typo in networkStatus API schema description property
• Bug 1911836 - Implement runtime.onUserScriptMessage and runtime.onUserScriptConnect: introduced new runtime.onUserScriptMessage and runtime.onUserScriptConnect API events
• Bug 1930196 - Deprecate browser.telemetry.registerScalars and browser.telemetry.{keyedScalar,scalar}{Set,Add} and replace them with no-ops: added deprecation notes on telemetry API method related to dynamically registered scalars
• Bug 1911833 - Implement initial MV3 userScripts API bindings: added Manifest V3 userScripts API schema
• Bug 1911835 - Implement USER_SCRIPT world: added USER_SCRIPT world to ExecutionWorld string enum
• Bug 1917000 - Implement opt-in to userScripts API: added "userScripts" to the OptionalOnlyPermission string enum

Firefox 135:

• Bug 1858078 - Add CSP support to JSON modules: added "json" resource type to DNR and webRequest API schema
• Bug 1937636 - Add a profiler feature for recording flow markers: added "flows" to the ProfileFeature strings enum

In addition to that this PR also includes:

• a temporary workaround on the addons-linter src/schema/updates/manifest.json side to prevent the empty enum currently part of the OptionalOnlyPermission schema data as imported from Firefox from triggering errors originated from ajv (which consider an empty array associated to an enum as invalid schema data) - see b417050
  • File bugzilla issue to remove the empty enum array from the API schema data imported from Firefox (tracked by Bug 1942814)
  • File github issue to remove the workaround along with the next Firefox 136 schema data import where the invalid empty enum array wouldn't be part of the data imported from Firefox anymore (tracked by Remove the workaround applied to the OptionalOnlyPermission type empty enum entry #5553)
• new tests to explicitly cover the behaviors expected on optional only permissions (when invalid due to being requested as non-optional and when valid due to being requested as optional)
  • File followup to consider adding a new error code to be associated specifically to the error to be reported when an optional only permission is being requested as non-optional and a better error message providing a link to docs describing how developers are expected to use optional only permissions in their extensions (tracked by Consider introducing a new error code for optional-only permissions #5554)

Fixes #5550

[rpl]

note: @willdurand this is currently covering the behavior expected at the moment without a more specific error code, I'd be leaning towards filing a separate followup to consider introducing a separate error code and a better error message linking a doc page with more precise guidance about how optional only permissions should be used by extensions developers.

[Rob--W]

File bugzilla issue to remove the empty enum array from the API schema data imported from Firefox

The type is defined there because we need to define the type at the manifest schema level, for it to be extensible by others. We cannot just remove it. That means that if an empty enum is really disallowed, that we need to think of alternatives.