Ensured the Page cache identifier is read in the same way and checking and saving the cache identifier

The change consists using a new model that pulls the design + store cache parameters. This model is injected in both places that needs these cache information. This has meant a plugin was removed in favour of this model.

Description (*)

When the page gets loaded, the FPC checks if the page cache identifier is already saved in the cache. This reading checks the server environment variables (eg: PARAM_RUN_CODE).
When the page has been rendered, the page cache identifier is saved to prevent the same page to be reloaded the next loads the same version for it. The identifier was currently saved differently to the identifier created in the reading phase and that was breaking the cache

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Built-in FPC cache is broken in 2.4.7 for some configurations #38626

Manual testing scenarios (*)

Test 1: Backward compatibility - The FPC works

Setup the Magento store with no environment variable PARAM_RUN_CODE, PARAM_RUN_TYPE, ensure the Full page cache is enabled and set the developer mode active, load a page twice and verify the second load is cached by checking the header X-Magento-Cache-Debug

Test 2: Test the fault - The FPC works with environment variables

Setup the Magento store with some environment variables PARAM_RUN_CODE, PARAM_RUN_TYPE, ensure the Full page cache is enabled and set the developer mode active, load a page twice and verify the second load is cached by checking the header X-Magento-Cache-Debug

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)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)