[Issue] Status of cache types changed after running setup:upgrade

[m2-assistant]

This issue is automatically created based on existing pull request: #28191: Status of cache types changed after running setup:upgrade

---

Description (*)

Fixed the issue that running bin/magento setup:upgrade re-enables layout, block_html and full_page caches.

Related Pull Requests

NA

Manual testing scenarios (*)

1. Disable cache types layout, block_html and full_page by running bin/magento cache:disable block_html full_page layout.
2. Run bin/magento s:up.
3. Enabling caches message displays in cli output and layout, block_html and full_page caches are enabled.
4. Expected result is those cache types should be disabled.

Enabling caches: Current status: Array ( [layout] => 1 [block_html] => 1 [full_page] => 1 )

Questions or comments

NA

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)

[m2-assistant]

Hi @ihor-sviziev. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[ihor-sviziev]

Duplicates #28186