Release new version with Hungarian translation fix

[chrsmutti]

What problem is this solving?

I merged #665 with manual version control thinking I would be able to recreate the same v3.132.0 version again, but there are some restrictions in place that prohibit pushes to master without PR. Creating this only to deploy a new version easily.

[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 🎉🎉

[github-actions]

Fails

🚫

We follow keepachangelog standards. Please, add a section to your changelog entry. Example: ## [Unreleased] + ### Fixed - Issue with image sizing in the SKU Selector. You can use one of the following sections: Added for new features. Changed for changes in existing functionality. Deprecated for soon-to-be removed features. Removed for now removed features. Fixed for any bug fixes. Security in case of vulnerabilities.

Generated by 🚫 dangerJS against ba1f41f

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 3.132.0 → 3.132.1

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 vtex.search-result@3.132.1

After that your app will be updated on all accounts.

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