Add ReCaptcha coverage for Contact GraphQL (SwiftOtter's SOP-348)

[lbajsarowicz]

Description (*)

According to the official documentation, Magento 2.4.7 comes without ReCaptcha coverage for Contact form GraphQL endpoint.

This Pull Requests fills this incomprehensible gap.

Fixed Issues (if relevant)

1. magento/magento2#<issue_number>: Issue title

Manual testing scenarios (*)

GraphQL call to verify:

mutation {
  contactUs(
    input: {
      email: "[email protected]",
      name: "Test User",
      telephone: "1234567890",
      comment: "This is a test comment."
    }
  ) {
    status
  }
}

Questions or comments

Contribution checklist (*)

• Author has signed the Adobe CLA
• 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)
• All automated tests passed successfully (all builds are green)

[lbajsarowicz]

@magento run all tests

[lbajsarowicz]

@ihor-sviziev Can you take a look?

[lbajsarowicz]

@ihor-sviziev @sivaschenko ?

[hostep]

Tagging @nathanjosiah, maybe he'll be able to move this PR forward

[ihor-sviziev]

I see in other places we have a || here. are you sure it should be &&?
Example: https://github.com/magento/security-package/blob/develop/ReCaptchaCustomer/Model/WebapiConfigProvider.php#L65-L69

[lbajsarowicz]

@ihor-sviziev After the research, I found out that \Magento\ReCaptchaSendFriend\Model\WebapiConfigProvider::getConfigFor is the most in-line with Contact form, that's why it's && not ||

[ihor-sviziev]

Why not "Contact", as a module name?

Suggested change

	<item name="contactUs" xsi:type="object">Magento\ReCaptchaContact\Model\WebapiConfigProvider</item>
	<item name="contact" xsi:type="object">Magento\ReCaptchaContact\Model\WebapiConfigProvider</item>

[lbajsarowicz]

Introduced change in the codebase.