Preparing v0.13.0a1 pre-release

[felipesanches]

• Profile owners, please take a look at the pending_review lists in your profile definitions. If you move them to exclude_checks it means you do not want the check in your profile. If you just remove from pending_review, then the check becomes effective in your profile. And if you do nothing, the checks still not reviewed will continue being automatically excluded from your profile.
• This release adopts a new naming scheme for checks. We had reports of users getting confused by the meaning of the reverse domain names included as prefixes of check-IDs, such as com.google.fonts. The real meaning was that the organization identified by such domain was the first contributor of a given check implementation. But some users were confused thinking that it mean the check belong to that organization's vendor-specific profile.
• Now profiles do not include that reverse domain prefix. And do not also have the "/check/" keywork anymore. As an example, com.google.fonts/check/tabular_kerning (on the Universal profile) is now simply called tabular_kerning
• Also, there's been a large number of checks migrated among profiles. Mosly towards the Universal one.
• The checks themselves also moved around in the code-repository, in an attempt to remove any resemblance of profile allocation within the /Lib/fontbakery/checks/ directory, which should be seen as a general pool of check implementations. As much as possible, profile definition should happen inside /Lib/fontbakery/profiles instead.
• The exception to this are the checks that are surely vendor-specific. All those were placed in sub-directories inside Lib/fontbakery/checks/, such as Lib/fontbakery/checks/vendorspecific/microsoft/.
• There may be additional migrations and renames of checks, before we make an actual v0.13.0 release. Please open an issue if you have suggestions of better names or better profile allocations.

---

Noteworthy code-changes

• [FontBakeryCondition:remote_styles]: Use the Google Fonts family name to fetch the family. (PR remote_styles: use Google familyname to fetch fonts #4838)

New checks

Added to the Google Fonts profile

• [googlefonts/axes_match]: Check the font isn't missing any axes and the axes have the same range as the Google Fonts version. (PR googlefonts/axes_match: check added #4836)

Changes to existing checks

On the Universal profile

• [unreachable_glyphs]: Avoid mutation of TTFont to fix issues with concurrent tests. (issue Multithreading causes errors in version 0.13.0a0 #4834)

On the Google Fonts profile

• [googlefonts/glyphsets/shape_languages]: Improve formatting of output to avoid excessively long reports. (issue [com.google.fonts/check/glyphsets/shape_languages]: Output is too long #4781)

Promotion of previously experimental checks

Made effective on the Universal profile

• • [varfont/instances_in_order]: "Ensure the font's instances are in the correct order." Was experimental since March/2024. (issue Check fvar instances are in the right order #3334)