Update Google Fonts collection data url for 6.7 release

[matiasbenedetto]

What?

The current Google font collection data is not up-to-date, with the latest additions to the list of available fonts and the latest versions of the existing ones. This PR updates the URL of the new file hosted on the WordPress.org CDN https://meta.trac.wordpress.org/ticket/7808 (pending).

Why?

To update the Google fonts collection data with the latest fonts and versions of those fonts.

Trac

Trac ticket: https://core.trac.wordpress.org/ticket/62258

---

These are some links for reference only.

Issues:
WordPress/gutenberg#64685
WordPress/google-fonts-to-wordpress-collection#34
https://core.trac.wordpress.org/ticket/62258
https://meta.trac.wordpress.org/ticket/7808

Data updates:
WordPress/google-fonts-to-wordpress-collection#38
WordPress/google-fonts-to-wordpress-collection#40

[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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props mmaattiiaass.

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

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[peterwilsoncc]

LGTM, thanks Matias.

I'll hold off clicking approve so I can test against w.org once the upstream commit is made.