WIP: Smarter collapse on DiffCollections to provide more files to the users

-- PLACEHOLDER --

If for the diff we consider one to be collapsed we are not going to render their data (which is the most consuming part) we can move up the limits based on the how collapse files we'll see because the most costly part is showing very large(lines/bytes) files.

I think is not a good behaviour collapse after any file is collapsed, what happens if it's the first one in the diff, you won't see anything. That could happen if all of them are quite big (which is what we're considering to collapse them for the UI).

What does this MR do?

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

What are the relevant issue numbers?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• CHANGELOG entry added
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the style guides
• Branch has no merge conflicts with master (if you do - rebase it please)
• Squashed related commits together Closes #19820 (closed)