Closes #7243: Preload fonts frontend

[Miraeld]

Description

Fixes #7243

This PR brings the front-end optimization to the newly added feature Preload Fonts.

Type of change

• New feature (non-breaking change which adds functionality).

Detailed scenario

None

Technical description

Documentation

This pull request introduces several changes to the inc/Engine/Media/PreloadFonts/Frontend/Controller.php file to implement font preloading functionality. Additionally, it includes updates to the test fixtures to ensure the feature works correctly.

Key changes:

Implementation of Font Preloading:

• Added UrlTrait to the Controller class to leverage URL-related utilities.
• Updated the optimize method to include logic for preloading fonts if the corresponding database row indicates fonts to preload.
• Introduced the preload_fonts, is_third_party_font, and preload_tag private methods to handle the generation of preload tags for fonts and determine if a font URL is third-party.

Test Fixtures Updates:

• Added new HTML test fixtures to simulate various scenarios for font preloading, including with cross-origin fonts and relative paths. [1] [2] [3] [4] [5] [6]
• Updated maybe_apply_optimizations.php to include new test cases for font preloading, ensuring the expected output matches the preloaded fonts scenario. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20]

Configuration Updates:

• Updated phpstan-baseline.neon to account for a new usage of apply_filters in the Controller.php file.

New dependencies

None

Risks

None

Mandatory Checklist

Code validation

• I validated all the Acceptance Criteria. If possible, provide screenshots or videos.
• I triggered all changed lines of code at least once without new errors/warnings/notices.
• I implemented built-in tests to cover the new/changed code.

Code style

• I wrote a self-explanatory code about what it does.
• I protected entry points against unexpected inputs.
• I did not introduce unnecessary complexity.
• Output messages (errors, notices, logs) are explicit enough for users to understand the issue and are actionnable.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
❌ -43.96% (target: -0.10%)	✅ ∅ (target: 50.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (eeaa286)	39257	17258	43.96%
Head commit (33d0397)	0 (-39257)	0 (-17258)	0.00% (-43.96%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#7312)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[wordpressfan]

This PR depends on the following PR:
#7304

I'm going to document this now to mention how to use the new approach, this will help a lot in preparing the head items not to print the tags directly and will adjust the ordering of preload, preconnect, ...etc. into head.

[wordpressfan]

The new way of printing head elements is documented here:
https://www.notion.so/wpmedia/New-rocket-head-structure-1a0ed22a22f080babda5dc0eff7ea21e