Fix typo in PHPDoc block

[jlnarvaez]

Description (*)

This PR remove a unknown referenced variable in PHPDoc for $helper variable declaration.

Manual testing scenarios (*)

This fix has no testing scenario, because is a code typo.

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)

Resolved issues:

1. resolves [Issue] Fix typo in PHPDoc block #38961: Fix typo in PHPDoc block

[m2-assistant]

Hi @jlnarvaez. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ 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.

[jlnarvaez]

@magento run all tests

[engcom-Hotel]

@magento create issue

[edenduong]

Thank you for your contribution!

[engcom-Dash]

QA is not required for this change since it only updates the property annotation for $helper.

Builds are failing so moving it to extended testing.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests

[engcom-Dash]

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

[engcom-Dash]

Functional test EE failures are different in the last two runs. Additionally, B2B build failure contains one known issue.
Issues 1

Function test B2B
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/38eb68aab93361bb013f820264130726/Functional/allure-report-b2b/index.html#categories/33b16da120eda74024a2e0f513c01ac4/70ec1976d2d60cac/

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/940e631d01d50c07e05b2d24e4ea3cc0/Functional/allure-report-b2b/index.html#categories/6f15b2b039379618445a7d928f9735df/54f0b7fb2360e01b/

Functional EE

Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/302b362edf5f92bb9abe90764f72fb08/Functional/allure-report-ee/index.html#categories/fa4393da515eaa6ecde572b60691d27d/6da05487bb65132a/

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/0624c439a571e823cdc01e0592fd9d81/Functional/allure-report-ee/index.html#categories/75b40a63f79830217aae704c6d6af940/fa606581008098c9/

Hence moving to merge in progress.

[engcom-Dash]

We have seen static failures in mainline PR after merging this PR into that. Hence for now moving this PR to Extended testing.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run Functional Tests CE, Functional Tests B2B

[engcom-Dash]

The Functional B2B and CE test failures seem flaky and some of these failures are known issues. They are neither part of PR nor failing because of PR changes. Hence moving it to Merge in Progress.

Functional Tests B2B
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/e1bbc12f72fa01682cde14fa159dfac4/Functional/allure-report-b2b/index.html#categories/3a3a8306986cbb01e5245b23e6e5b238/996200decbb7a5c7/

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/6934cf60fd6c7cef4507f8d7fbd26573/Functional/allure-report-b2b/index.html#categories/3a3a8306986cbb01e5245b23e6e5b238/4dd181dc3e36010e/

Known Issues:
MultiShippingWithCreationNewCustomerAndAddressesDuringCheckoutTest: ACQE-7229
StorefrontQuoteCanBeRenamedUntilLockedTest: ACQE-7137
StorefrontReuseCouponCodeAfterOrderCanceledTest: ACQE-7230

Functional Tests CE
Run 1: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/385317a8db0b9c1ce1e648b548abe475/Functional/allure-report-ce/index.html#categories/6d7e37752c3cc83cb3d2063131f608bb/10905c554d99cfb5/

Run 2: https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/38940/879df41645730b1387108b756f8c6aa1/Functional/allure-report-ce/index.html#categories/8fb3a91ba5aaf9de24cc8a92edc82b5d

Known Issue:
VerifyDefaultWYSIWYGToolbarOnProductTest: ACQE-7227