Fix admin grid filter backslash escaping issue

[wubinworks]

Fixed admin grid filter backslash escaping issue.

Description (*)

The Admin Grid Filter cannot return correct result for keyword that contains backslash. For example Magento\Store.
This pull request fixed it by escaping backslash.

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes [Small Bug] Filter of Admin Panel listing component cannot hit when field value contains \ #39513

Manual testing scenarios (*)

1. Create a new block in CMS block admin grid with title Magento\Store.
2. Input Magento\Store in title filter to search and then check the search result.
3. The result should contain Magento\Store after merging this branch.

Questions or comments

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 @wubinworks. 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.

[wubinworks]

@magento run all tests

[wubinworks]

@magento run all tests

[engcom-Hotel]

Hello @wubinworks,

Thanks for making the changes!

Some static tests are still failing, please fix those as well.

Thanks

[wubinworks]

@magento run all tests

[engcom-Bravo]

@magento run all tests

[engcom-Bravo]

Hi @wubinworks,

Thanks for the collaboration & contribution!

✔️ QA Passed

Preconditions:

• Install fresh Magento 2.4-develop

Steps to reproduce

• Create a new block in CMS block admin grid with title Magento\Store.
• Input Magento\Store in title filter to search and then check the search result.
• The result should contain Magento\Store after merging this branch.

Before: ✖️ 

After: ✔️

Builds are failed. Hence, moving this PR to Extended Testing.

Thanks.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE, Integration Tests, Unit Tests

[engcom-Dash]

The Functional B2B failures has one consistent failure and its a known issue. Other failures are inconsistent and flaky. They neither part of PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/f640e9123e4444be84529a623f24ce76/Functional/allure-report-b2b/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/581c0dc6c179d036e34c2a3a9306033c/Functional/allure-report-b2b/index.html#categories/bdbf199525818fae7a8651db9eafe741

Known Issue: StorefrontProductNoLongerVisibleInWishlistOnceUserUnassignedFromCompanyTest ACQE-8287

The Functional EE failures are inconsistent and flaky. They neither part of PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/8bec2d6ecbfdfd3f8e16409dca02e33e/Functional/allure-report-ee/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/36f2be1c96803a869321072fc866f072/Functional/allure-report-ee/index.html#categories/bdbf199525818fae7a8651db9eafe741

Consistent Unit Test Failures are know issue and JIRA has been raised for the same.They neither part of PR nor failing because of the PR changes.

Build 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/a299d4232c05dc1e7ececa5621625feb/Unit/console-error-logs.html

Build 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/39535/53b85cfd219f6827ab5f1adfb63233c9/Unit/console-error-logs.html

Known Issue: https://jira.corp.adobe.com/browse/ACP2E-4051

Hence moving this PR in Merge In Progress.