Add explanatory titles to cache management buttons

[YevhenZvieriev]

Description

This Pull Request adds explanatory titles to cache management buttons on the Cache Management page. The added titles provide users with a better understanding of the functionality of each button, making their interaction with the cache management buttons more intuitive. These changes improve the user experience and provide a better understanding of the functionality of cache management buttons on the Magento admin page because at first glance it is not clear what the difference between these two buttons is.

Changes

Added explanatory titles to the Flush Cache Storage and Flush Magento Cache buttons.

The title for the Flush Cache Storage button when you move the cursor over it now explains that it performs similar actions as the bin/magento cache:flush command:

The title for the Flush Magento Cache button when you move the cursor over it now explains that it performs actions similar to the bin/magento cache:clean command:

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)

Resolved issues:

1. resolves [Issue] Add explanatory titles to cache management buttons #38607: Add explanatory titles to cache management buttons

[m2-assistant]

Hi @YevhenZvieriev. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

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

[engcom-Hotel]

@magento create issue

[YevhenZvieriev]

@magento run all tests