Keep TAGS_LIMIT in sync for TaggableQueries

Ref: #338479 (closed)

What does this MR do?

This MR makes sure we keep in sync both area of the codebase when dealing with processing jobs and our new tags limit introduced in !68380 (merged).

Why are we doing this?

If we want to lower this limit in %15.0 it could be easy to forgot all the different areas of the codebase that needs to be updated.

As Kent Beck said for each desired change, make the change easy (warning: this may be hard), then make the easy change

Does this MR meet the acceptance criteria?

Conformity

• [-] I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
• [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• [-] This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.