cacheTags not applied consistently in Admin UI

[SimonVreman]

Describe the Bug

Previously, in #10319, the cacheTags setting was added. It was however only applied to the edit thumbnail, not to preview sizes and cropping.

Link to the code that reproduces this issue

PR already opened #10801

Reproduction Steps

Identical to the previous issues, however, check not only the edit thumbnail, but also 'preview sizes' and 'cropping'.

• CloudFront InvalidQueryStringException on Upload's "Edit" view thumbnail #9880
• Image Preview is not working for Media #9993
• imageCacheTag does not check URL for already present parameters #10139

Which area(s) are affected? (Select all that apply)

area: ui

Environment Info

Payload: 3.17.1
Next: 15.1.2
Node: 20.11.0

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[SimonVreman]

Hidden in the issue body, I already opened the PR to fix this two weeks ago: #10801