Update classes and interfaces part 3

[sivaschenko]

Update the following classes and interfaces in 2.5-develop branch:

1. Magento\Checkout\Model\Type\Onepage Create a new interface and move constants there. Current class must implement the new interface to maintain backward compatibility
2. Magento\Framework\Image\AdapterFactory Change visibility of protected properties to private
3. Magento\Catalog\Model\Config Change visibility of protected properties/methods to private
4. Magento\Customer\Model\CustomerRegistry Change visibility of protected properties/methods to private
5. Magento\Quote\Setup\QuoteSetup Change visibility of protected properties/methods to private
6. Magento\Ui\Component\Control\Container Change visibility of createButton() method to private
7. Magento\Catalog\Model\Layer\Filter\Item Change visibility of protected properties/methods to private

[m2-assistant]

Hi @sivaschenko. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues 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 issues 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

[ProkopovVitaliy]

@magento i am working on this

[Usik2203]

@magento I am working on this

[magento-engcom-team]

✅ Confirmed by @engcom-Oscar
Thank you for verifying the issue. Based on the provided information internal tickets MC-41934 were created

Issue Available: @engcom-Oscar, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.