Visual assets code repository

Description

A new project-level repo to manage visual assets, such as images in various formats, and video.
This would be at the same level as issues and merge requests.
It could be called Visual Assets. And it would be implemented as a repository so that you have versioning on the assets.
It would be highly integrated with issues, as specified in
In particular the use cases is that during product development, you want to have items such as mockups integrated with discussions in issues. This elevates visual assets to a first-class citizen in the product development stages of planning. Note that this is different from actual code assets that are pushed to production in a project. Those assets should live in the existing code repo, as usual.
Note that at the project level, there is the regular code repository, called Repository. This contains the git versioned code that is pushed into production.
There is a Wiki, that is also version controlled in the background.
With this issue, we are creating another repo for managing visual assets.

We need UX designs to figure out how to manage these visual assets.
How the visual assets integrate with issues are specified in
We need technical designs and considerations on how to implement the repo and how it would impact storage for projects.
There are ~Platform implications in terms of that storage.