Incorrect processing of unicode ranges

This conversation started here, so please check it first:
- [Stack Overflow question (with answer)](https://stackoverflow.com/questions/66138075/the-web-version-of-the-noto-serif-font-seems-to-be-missing-the-dagger-character/66181786)
- https://github.com/googlefonts/noto-fonts/issues/2004

Seems like Google Font API not correctly work with Unicode ranges. [‡ Double Dagger](https://unicode-table.com/en/2021/) has U+2021 Unicode number, and it's a part of the [General Punctuation Unicode subset](https://unicode-table.com/en/blocks/general-punctuation/) which using range between 2000—206F. Google Font includes this range inside _latin_ subset:

```
@font-face {
font-family: 'Noto Serif';
font-style: normal;
font-weight: 400;
src: url(https://fonts.gstatic.com/s/notoserif/v9/ga6Iaw1J5X9T9RW6j9bNfFcWaDq8fMU.woff2) format('woff2');
unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+2000-206F, U+2074, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
}
```

But the font file, fetched with config above, doesn't include a glyph for U+2021 symbol: