[Issue] Add WEBP + AVIF Support by default

[m2-assistant]

This issue is automatically created based on existing pull request: #32400: Add WEBP + AVIF Support by default

---

Webp should already be set up by default

Steps to reproduce:

1. Add webp, avif, etc files to lib/web/images directory.
2. Modify app/code/Magento/Backend/view/adminhtml/layout/admin_login.xml file to use webp, avif, etc file as Magento 2 logo (edit "logo" block "logo_image_src" argument value).
3. Flush cache.
4. Check webp, avif, etc file is used as Magento 2 logo on the admin login page.

[magento-engcom-team]

✅ Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-41352 were created

Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[m2-assistant]

Hi @engcom-Oscar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

• 1. Add/Edit Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 2. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[gabrieldagama]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #32400 by @in-session in 2.4-develop branch
Related commit(s):

• 59a5e8d5d4f8fe1e9e9b04b5d73e95e2750b75f9
• f578f02d346379a8ff0c1f79732a9943a2d394be
• 59161f29dd0fd857430907ddc8f21b9cea456048
• 81882e7842435b969c04c5d30daab7cc385fdd79
• 73f6c3fdbce4e7a661ecad5a2a75959031f210d1
• 7e4e0749ba07a182983e4c12cc15b76232cab8e2
• 760ab3680d02b0b334094b9bf81bca7fbae6b6fa
• 1e5cf5ba51c134bc889a962ccc2e6bbd35349f70
• c4bc0c1ed93fd80eb3d7b3680f26a4bd71464339
• c3f72621a3cf3e016c5b202f2db88c1e82b10406
• 28f539b1e75c9ec9258dcd24c68b2d3aa7333e2f
• 27c93abf3626cc8aaea36dbbd7179bbf4ac35d8c
• 8f4e06f380a0a9f841698ed5296319219398fdbd
• 99938447a4b4758baeb076e8820487c248954f3d
• d2bd6cfabd58a39a39cb1cc8d3495a27dd4bb7f1
• d265e960c5bde8286a818346132470d0cf6e224c
• 203dbf46960e26f3f80891c9059a43d5953e8760
• 73c94d41f7ab8b27a4231628b214b8e9bf17f271
• c416e6b8b7b2c5c1bb8429ea363622b216810bf4
• b877a4a997051d36360e8cb58bbe0f3431d9c2e9
• 3530c6cfd2229caa48862bdf5aed96f047af7777
• ea1f90a84b9fd8133d5e6d7ecb8a152f4ceb2afb
• 9c8c61b07264f177df8333136b930b8c2fda1446
• 896082355682e9adde6f09dd11b0e4c29d51cc42
• 9d778c8f472cb2a2b8ea57219c36fcebcef2b284
• 8313833d6e2337b759af23e9b8b1b373a4824210
• de5c55840508d4f645a21e1200d61e93d833da07
• 5188dcf8bd36d49229ef01632b62e4b58247dae5
• 22643ae2a5041701b43dcd416a185c836ebbdd58

The fix will be available with the upcoming 2.4.3 release.