Hashed storage attachments migration path

What does this MR do?

Make Hashed Storage migration logic incremental (first it will migrate the repository then it will migrate the attachments.

Add additional rake tasks to gitlab:storage namespace to help visualize and trigger migration to Hashed Storage for attachments as well.

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

Why was this MR needed?

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests added for this feature/bug
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Squashed related commits together
• Internationalization required/considered

What are the relevant issue numbers?

Related to gitlab-org/gitlab-ee#3674