Tests: Assert unsupported requests for font collections controller

[shail-mehta]

Part of: #66073

What

Replaces empty @doesNotPerformAssertions create/update/delete stubs in Tests_REST_WpRestFontCollectionsController with real negative assertions.

Each unsupported request asserts rest_no_route with status 404, using an authenticated administrator and a valid item fixture (mock-col-slug).

Updated file: tests/phpunit/tests/fonts/font-library/wpRestFontCollectionsController.php

Why

The font collections controller only registers readable collection and item routes. Empty abstract-method stubs hide whether unsupported write operations are actually rejected, and the annotation count keeps growing.

This continues the agreed approach from [64004] / [64075] / [64076] on another conventional read-only controller, before any broader WP_Test_REST_Controller_Testcase change.

How

• POST /wp/v2/font-collections → rest_no_route / 404 (collection is GET-only)
• POST / PUT / PATCH /wp/v2/font-collections/mock-col-slug → rest_no_route / 404 (item is GET-only; asserts GET 200 first so the path is proven valid)
• DELETE /wp/v2/font-collections/mock-col-slug → rest_no_route / 404 (asserts GET 200 first)
• Left prepare_item() unchanged (held for further discussion)
• Did not change the abstract base class yet

Testing instructions

1. Start the local WordPress develop environment.
2. Run: npm run test:php -- --filter Tests_REST_WpRestFontCollectionsController

Use of AI tools

Cursor

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

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