Interactivity API: Turn named capturing groups back into numbered ones inside toVdom

[DAreRodz]

What?

Reverts a recent change in dbf231a that introduced named capturing groups in the RegExp used to parse directive values.

gutenberg/packages/interactivity/src/vdom.ts

Lines 98 to 103 in dbf231a

	const regexResult = nsPathRegExp.exec(
	attributes[ i ].value
	)?.groups;
	const namespace = regexResult?.nameSpace ?? null;
	let value: any =
	regexResult?.value ?? attributes[ i ].value;

Why?

According to caniuse.com, named capturing groups have global support of 95.62%. Although the value is quite high, there could be users for whom the Interactivity API does not work just by using this feature.

For instance, global support of Proxy objects is 97.28%.

How?

Using numbered capturing groups instead.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: DAreRodz <darerodz@git.wordpress.org>
Co-authored-by: sirreal <jonsurrell@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[DAreRodz]

I've added the [Type] bug label, but I'm not sure if that's the correct one. Should it be [Type] Enhancement instead?

cc: @sirreal

[sirreal]

I didn't test, but the changes look good.

[sirreal]

Nit: I don't love this name, maybe regexResult?

[DAreRodz]

Done in 6456504.

[sirreal]

We can leave it bug, I've also added a Gutenberg backport label because it would be nice to get this out in a patch version if there is one.