Feature/allow skipping caching

[darylldoyle]

Description of the Change

This pull request improves the logic for enabling or disabling the class loader cache in the module initialization process, making it more flexible and testable. The main change is the introduction of a new method that centralizes the decision for using the cache, along with updated documentation and comprehensive tests.

Class loader cache logic improvements:

• Added a new protected method should_use_cache() in ModuleInitialization.php to determine whether the class loader cache should be used, based on environment type and specific constants. This replaces the previous inline logic and allows for easier testing and extension.
• Updated the cache usage condition in the get_classes() method to use the new should_use_cache() method, improving clarity and maintainability.

Configurability and documentation:

• Updated the documentation in Modules-and-Initialization.md to describe how to disable class caching using the new TENUP_FRAMEWORK_DISABLE_CLASS_CACHE constant, especially for hosts that do not support file-based caching.

Testing enhancements:

• Added a series of tests in ModuleInitializationTest.php to cover all branches of the new should_use_cache() logic, ensuring correct behavior under different environment conditions and constant definitions.
• Imported the Brain\Monkey\Functions\stubs utility in the test file to facilitate function stubbing for environment simulation.

How to test the Change

Run the PHPUnit tests

Changelog Entry

• Added - New option to disable file-based caching

Credits

Props @darylldoyle, @fabiankaegy, @dustinrue

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• All new and existing tests pass.

[fabiankaegy]

Lol.... I literally just now created #27 😂 😂 😂 😂

[fabiankaegy]

But your's is much nicer so I'll close mine 👍

[fabiankaegy]

Thanks for this! :)