remove invalid character validation from searchMetadata query

[hiagolcm]

What problem is this solving?

Previously, a character validation for special characters like &[]/?= was added to the productSearch query to support legacy behavior before intelligent search was introduced.

This same validation was mistakenly copied to the searchMetadata query. I've removed it, as testing confirmed that all special characters are now handled correctly and the validation is no longer needed.

How should this be manually tested?

Workspace

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

• There's nothing new to document 🤔
• I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

• I just updated 🎉🎉

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 1.88.1 → 1.88.2

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy [email protected]

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖