Co-authored-by: Guillermo Fuentes <guillermofuentesquijada@gmail.com>

…ions/validators.ru.xlf:471

This PR was squashed before being merged into the 6.4 branch.Discussion----------[Notifier] Fix Clicksend transport| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        | Fix#52486| License       | MITHello,It seems to be an old issue (see#52486) but the format sent to Clicksend is not correct. When using the library we have this error: `[Symfony\Component\Notifier\Exception\TransportException]  Unable to send the SMS - "{"http_code":400,"response_code":"BAD_REQUEST","response_msg":"The messages array is empty.","data":null}"`. The correct structure should have a "messages" key (see documentation:https://developers-dev.clicksend.net/docs/messaging/sms/other/send-sms).Commits-------734e60a [Notifier] Fix Clicksend transport

This PR was merged into the 6.4 branch.Discussion----------[Messenger] fix: Add argument as integer| Q             | A| ------------- | ---| Branch?       | 6.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        || License       | MIT## DescriptionAdded an argument ('x-delivery-limit') to the ARGUMENT_AS_INTEGER array. This change was made to ensure compatibility with RabbitMQ, as the argument was previously being sent as a string, which caused errors. By adding it to the ARGUMENT_AS_INTEGER array, the argument is now properly sent as an integer instead of a string, resolving the issue.Commits-------4cdbbe5 fix: Add argument as integer

This PR was merged into the 6.4 branch.Discussion----------[Validator] update Russian translation| Q             | A| ------------- | ---| Branch?       | 6.4 <!-- see below -->| Bug fix?      | no| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->| Deprecations? | no <!-- please update UPGRADE-*.md and src/**/CHANGELOG.md files -->| Issues        |#60469   <!-- prefix each issue number with "Fix #", no need to create an issue if none exists, explain below instead -->| License       | MIT<!--Replace this notice by a description of your feature/bugfix.This will help reviewers and should be a good start for the documentation.Additionally (seehttps://symfony.com/releases): - Always add tests and ensure they pass. - Bug fixes must be submitted against the lowest maintained branch where they apply   (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the latest branch. - For new features, provide some code snippets to help understand usage. - Changelog entry should followhttps://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry - Never break backward compatibility (seehttps://symfony.com/bc).-->Commits-------7e09dc0 validate translate src/Symfony/Component/Validator/Resources/translations/validators.ru.xlf:471