Expose all artifacts sizes in jobs api

What does this MR do?

Adds also trace and metadata sizes to jobs API.

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

Not that I'm aware of.

Why was this MR needed?

Project storage statistics grew extremely after trace archivation during migration to 11.0.x. Without this MR the user has no change to know why project statistics show so large artifacts storage consumption suddenly.

See #49368 (moved)

Screenshots (if relevant)

n/a

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Conforms to the code review guidelines
  • Has been reviewed by a UX Designer
  • Has been reviewed by a Frontend maintainer
  • Has been reviewed by a Backend maintainer
  • Has been reviewed by a Database specialist
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• If you have multiple commits, please combine them into a few logically organized commits by squashing them
• Internationalization required/considered
• End-to-end tests pass (package-and-qa manual pipeline job)

What are the relevant issue numbers?

Part of #49368 (moved)