[Issue] Static properties serialization fix.

[ghost]

This issue is automatically created based on existing pull request: #26175: Static properties serialization fix.

---

Preconditions(*)

When test cleanup is disabled, Magento\TestFramework\Workaround\Cleanup\StaticProperties is caching static variables before the integration test starts, and restoring them after the test run is finished (if some instance of \Magento\TestFramework\TestCase\AbstractController has run).
Serialization and unserialization of static properties are provided by Magento\Framework\Serialize\Serializer\Json class, which wraps json_encode and json_decode functions.
Some of static properties are objects (e. g. \Magento\Framework\Autoload\AutoloaderRegistry::$autoloader). After encoding and decoding these properties through JSON we are getting arrays instead of objects. So we are facing issues on consecutive runs of integration tests.

Fixed Issues (if relevant)

1. None

Steps to reproduce(*)

1. Disable the application cleanup in integration tests phpunit.xml:
   <const name="TESTS_CLEANUP" value="disabled"/>
2. Run some controller integration test (e. g. \Magento\Newsletter\Controller\ManageTest)
3. Run some another controller integration test (e. g. AdminNotification test bundle)

Actual Result:

Expected Result:
tests should run successfully

Questions or comments

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)

[magento-engcom-team]

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

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

[magento-engcom-team]

Hi @m2-backlog[bot]. Thank you for your report.
The issue has been fixed in #26175 by @p-bystritsky in 2.4-develop branch
Related commit(s):

• 9383fe1e8933adf30e0f18be383738719856442f
• 3343d815c472354e44de9280d845e4917bbd5d0e
• 7388d8cfd5702178f902ec7c0598d57317767536
• 6bf711b172e38d002221a9e8663048a2926be600
• edfaf7c0a0f3e0905736a840bc6983fc07a464f8
• c6244eafadc97911cc5f56f9f88b90a568c6cf2b
• 3b7f7589f4ea233b2c38d30242368f46aabb8cce
• 37b852d9fed4b5b7c24d8a1b8b5fa3f1dc2de322
• 921019290db127940e8c7d4691bc14f7ff8f6c3d

The fix will be available with the upcoming 2.4.1 release.