[Admin] Search for projects and show project details

[laushinka]

Admin page should allow searching of projects by entering the repo or the slug.

(The following screenshot is just a placeholder - this will need more design decisions)

Search

• sub-string match anywhere in the cloneUrl (assuming this is possible, and OK for DB performance)
• nice-to-have: match on slug

Search results

• list entries show name (link to project detail), cloneUrl (link to git provider)
• list ordered by created date
• list ordered by updated date

Project details

• page URL is /admin/projects/project-id
• name
• repository (from cloneUrl)
• incremental prebuilds (from settings)
• owner
• team
• created date
• list of prebuilds

Prebuild details

• page URL is /admin/prebuilds/prebuild-id
• same content (with prebuild log) as in projects UI

[laushinka]

With Prebuilds	No Prebuilds

[laushinka]

@jldec @gtsiolis How Project Detail looks like in progress 👆🏼

[laushinka]

@jldec @gtsiolis And this is what the search list looks like in progress:

[gtsiolis]

Thanks for the update, @laushinka! I'm posting below the current state of the designs, after catching up with @jldec earlier today, see relevant document (internal). Feedback is welcome!

Projects List	Project Details

[laushinka]

I'm posting below the current state of the designs, after catching up with @jldec earlier today

@gtsiolis Thanks! Some questions:

1. Where would we put the information on incremental prebuilds and whether it's deleted?
2. Do teams also have an avatar? In case the owner is a team?

I also wonder whether this new design layout can be implemented later for all of the user and workspace details in the same ticket, so we have a consistent look in one release?

@jldec In the tasks list in the description, we have the prebuild details as well. Do we want this in this ticket too? Or should this ticket be the MVC for the project search? Reusing the components are not that straightforward, as every method call needs to be created and adjusted for admin actions as well. I'm fine with working on them, but also would be happy to see the most important things shipped.

[jldec]

I looked at the current implementation with @laushinka using the implementation in #7882

• The project list with 3 columns: name, cloneUrl, and created, works well
  Let's keep that design for now, and switch to name-above-with-git-provider/org-below in a separate ticket when we have a consistent way to do that across lists.
• Similarly, the project detail which follows the layout from workspaces, and includes user and team in 2 separate values, works well. We can upgrade to a user-or-team pattern later.
• The prebuild detail can be added separately - for this first implementation just showing the prebuild list below the project is already a big step forward for admins.

[gtsiolis]

Thanks, @laushinka @jldec! Agree with #7636 (comment). Just posted some review comments in #7882 (review).