Add CartItemOptionsProcessor to Magento_Quote's API

[navarr]

Description (*)

This class is used by at least one VBE and is necessary for loading Cart Item Options for quotes that are not "active" (for example, when wanting to retrieve option information for an order that has already been placed)

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)
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Add CartItemOptionsProcessor to Magento_Quote's API #30831: Add CartItemOptionsProcessor to Magento_Quote's API

[m2-assistant]

Hi @navarr. Thank you for your contribution
Here is some useful tips 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

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[sidolov]

@magento create issue

[mrtuvn]

I think you can change this PR branch to 2.5-develop branch
CC @sivaschenko @gabrieldagama consider this can be mark as API

[navarr]

@mrtuvn This PR backdates the @api annotation all the way to Magento 2.1.0; so I don't think the branch matters that much

[sivaschenko]

@navarr thanks for the PR! I think @mrtuvn is right, we wouldn't like to introduce new marked API to patch releases so this PR should be targeted to 2.5-develop. Also, since annotation is not needed, it should be set automatically during the release process for new API.

[navarr]

@sivaschenko Updated.

[sivaschenko]

@navarr thank you!

[sivaschenko]

Approved in scope of magento/architecture#473, priority increased to P1

[sivaschenko]

@magento run Static Tests

[magento-engcom-team]

Hi @sivaschenko, thank you for the review.
ENGCOM-8764 has been created to process this Pull Request
✳️ @sivaschenko, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests