Fix: Correct getPathInfo usage in captcha deletion cron

[satishashilwar]

The DeleteExpiredImages cron was not working since Magento 2.4.8 due to incorrect usage of getPathInfo() method. The method was called with a second parameter (PATHINFO_EXTENSION) which it doesn't support, causing the PNG file extension check to always fail.

Changes:

• Fixed getPathInfo() call to use array indexing instead of second parameter
• Changed from getPathInfo($filePath, PATHINFO_EXTENSION) == 'png'
• Changed to getPathInfo($filePath)['extension'] == 'png'
• Added comprehensive unit test to verify correct getPathInfo usage

Root cause:
The getPathInfo() method only accepts one parameter and returns the full pathinfo array. Using PATHINFO_EXTENSION as second parameter was comparing array to string, which always resulted in false.

Manual testing:

1. Enable captcha on frontend/admin login
2. Generate captcha images by failing login attempts
3. Wait 20+ minutes (default timeout)
4. Run bin/magento cron:run --group=default
5. Verify PNG files are deleted from media/captcha/ directories

Before fix: Files never get deleted, directory grows indefinitely
After fix: Expired PNG files are properly cleaned up

Fixes: #40192

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @satishashilwar. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[satishashilwar]

@magento run all tests