Add Heblock

Font Project Git Repo URL:

https://github.com/tamirpomerantz/heblock-font

Release 1.000: https://github.com/tamirpomerantz/heblock-font/releases/tag/1.000

Heblock is a geometric Hebrew and Latin sans for everyday use (presentations, headlines, interfaces, and running text). Hebrew is original (Tamir Pomerantz), drawing inspiration from Narkiss and Arial; Latin is based on [DM Sans](https://fonts.google.com/specimen/DM+Sans) (Colophon Foundry / Jonny Pinhorn), with selected Latin letters adjusted so both scripts form one system. Nine static weights, Thin–Black (100–900). Menu name: Heblock.

This is submitted as a new family, not as a PR to [dm-fonts](https://github.com/googlefonts/dm-fonts): the Hebrew is not a DM Sans translation, the Latin masters were changed to sit with the Hebrew, and the family is meant as a bilingual system rather than a Hebrew add-on to DM Sans. It ships static (not a variable font) because instance RoundCorner filters are part of the design; sources are sources/Heblock.glyphs, built with gftools.

**Requirements:**
By opening this issue, I confirm the project meets the following requirements:

- [x] The entire font project is available in a Github repository (repo) and licensed under the [OFL](https://openfontlicense.org/open-font-license-official-text/)
- [x] I confirm that by 'entire font project', no "plus" or "pro" or other larger version of the project exists as a retail font anywhere
- [x] The source files are available in the repo
- [x] I am the sole copyright author of the entire project, or all other copyright authors have licensed their work to me under the OFL, and I commit to clearly disclosing if AI tools were used in the creation of this project.
- [x] There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
- [x] The family name is unique according to [namecheck.fontdata.com](https://namecheck.fontdata.com/)
- [x] The name of the font family expected to appear on app menus must be very clearly communicated and definitive. It should not include any copyright holder's full names or acronyms.
- [x] The font supports at least the Google Fonts 'Latin Core' glyphset from [github.com/googlefonts/glyphsets](https://github.com/googlefonts/glyphsets) ([direct link](https://github.com/googlefonts/glyphsets/blob/main/data/results/txt/nice-names/GF_Latin_Core.txt))
- [x] The repo has the [Google Fonts preferred upstream repo structure](https://googlefonts.github.io/gf-guide/upstream.html)
- [x] I have read, agree with, and comply with, the full [Google Fonts contributing requirements](https://googlefonts.github.io/gf-guide/index#pre-production-getting-your-fonts-ready-for-gf)
- [x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)

**Image:**

Start by reviewing the linked heblock-font repository, especially sources/Heblock.glyphs, the documentation/specimen.png, and the release tagged 1.000. Check the repository structure, OFL licensing, glyph coverage, and Google Fonts contributing requirements before determining whether the family is ready for onboarding. Done means the submission satisfies the stated requirements and can proceed through review.

Written by the indexing model from the issue text.