fix/removed etag generation for html response

[Abhishek-17h]

[!CAUTION] The Volto Team has suspended its review of new pull requests from first-time contributors until the release of Plone 7, which is preliminarily scheduled for the second quarter of 2026. Read details.

---

• [x] I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
• [x] I verified there aren't other open pull requests for the same change.
• [x] I followed the guidelines in Contributing to Volto.
• [x] I succesfully ran code linting checks on my changes locally.
• [x] I succesfully ran unit tests on my changes locally.
• [x] I succesfully ran acceptance tests on my changes locally.
• [ ] If needed, I added new tests for my changes.
• [ ] If needed, I added documentation for my changes, either in the Storybook or narrative documentation.
• [x] I included a change log entry in my commits.

---

If your pull request closes an open issue, include the exact text below, immediately followed by the issue number. When your pull request gets merged, then that issue will close automatically.

Closes #7094

[Abhishek-17h]

@tiberiuichim Instead of completely disabling estag , we’ve now disabled it only for HTML responses, since it wasn’t effective due to the dynamic nature of the HTML content. I attempted a complete solution by trying to generate a consistent ETag, but the ordering of object keys in window.__data is not reliable and I didn't found any way to make it possible after trying multiple option. Even though we can make redux router key static ,as it is not required in SSR of page but it is not sufficient to make estag generation consistent.

[github-actions[bot]]

Hi There! 👋

We haven't seen any activity on this pull request in a while :sleeping:, and we want to make sure that it's still relevant. Please let us know by:

• adding a comment about what needs to be done next 💬
• updating its status and other labels 🏷️

Otherwise close this pull request. 🧹