Fonts not differentiated by unicode-range

[strarsis]

Description

Fonts that are registered with the Fonts API (including by theme.json) are currently not differentiated by the unicode-range.

convert_variation_into_handle only uses the font-weight and font-style for generating a handle, not unicode-range.
https://github.com/WordPress/gutenberg/blob/trunk/lib/experimental/fonts-api/class-wp-fonts-utils.php#L53

Just adding unicode-range to the array of processed properties solves the issue. But unicode range normalization may be required to ensure that fonts with same unicode-range but differing notation of the unicode-range are treated as identical.

Step-by-step reproduction instructions

1. Declare two font files for a font-face with same parameters, except for a unicode-range.
2. Notice that the font face of only one font file is eventually enqueued, all the other font files will not be usable.

Screenshots, screen recording, code snippet

No response

Environment info

No response

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

Yes