refactoring lazy loading strings

Description:
The current implementation of Lazy Loading functions as expected on non-ELPM devices, but encounters issues when used on ELPM devices. It is crucial to ensure compatibility across both types of devices for a seamless user experience. Additionally, the overall concept of managing strings can be revised, while preserving the functionality of caching strings in RAM, freeing them randomly, and automatically reloading them when needed.

User Story:
As a developer, I need the Lazy Loading feature to work consistently on both non-ELPM and ELPM devices, and to have an efficient string management system that caches strings in RAM, frees them randomly, and reloads them when required, to ensure optimal memory usage and performance.