Modern Image Formats: link to FAQ from settings section

[Gilmoursa]

Summary

Fixes #2442.

Users frequently open support topics confused about why their uploads aren't generating AVIF/WebP files. The FAQ in readme.txt already explains the primary reason (the plugin discards converted images that would be larger than the original), but there was nothing in the admin UI pointing users there.

This adds a brief note with a link to the plugin FAQ on WordPress.org in the Modern Image Formats settings section on Settings > Media, so users can find the explanation without having to search the support forums.

The section previously used __return_empty_string as its callback (no description rendered). This replaces it with a dedicated callback that outputs a single sentence linking to the FAQ.

Changes

• plugins/webp-uploads/settings.php: replace __return_empty_string section callback with webp_uploads_modern_image_format_settings_section_callback() which renders a FAQ link
• plugins/webp-uploads/tests/test-settings.php: add test asserting the callback outputs the FAQ URL and an anchor tag

Test plan

• Navigate to Settings > Media with the Modern Image Formats plugin active — confirm a note with a link to the FAQ appears under the "Modern Image Formats" section heading
• Confirm the link points to https://wordpress.org/plugins/webp-uploads/#faq
• Run the unit tests: composer test:integration -- --filter test_webp_uploads_modern_image_format_settings_section_callback

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

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Gilmoursa <gilmoursa@git.wordpress.org>
Co-authored-by: westonruter <westonruter@git.wordpress.org>
Co-authored-by: b1ink0 <b1ink0@git.wordpress.org>

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.86%. Comparing base (347597f) to head (bf1b6eb).
⚠️ Report is 5 commits behind head on trunk.

Additional details and impacted files

@@            Coverage Diff             @@
##            trunk    #2480      +/-   ##
==========================================
+ Coverage   69.33%   69.86%   +0.52%     
==========================================
  Files          90       90              
  Lines        7749     7759      +10     
==========================================
+ Hits         5373     5421      +48     
+ Misses       2376     2338      -38     

Flag	Coverage Δ
multisite	69.86% <100.00%> (+0.52%)	⬆️
single	35.68% <0.00%> (-0.05%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[westonruter]

I think a closure here would make more sense than a global function.

[westonruter]

FYI: we use n.e.x.t for version numbers and then update them before a release.