[Spike] Investigate potential architecture for an improved Commit list (frontend)

Context

With the interest of clarifying the level of effort, we'd like to dive into the frontend of how an improved Commit list (example) could look like.

There will be a separate effort to identify the Backend effort for this, which will follow the findings of this spike.

Goal

Indentify the steps necessary to build the Frontend in a sustainable way reusing existing components

Research

Incomplete list of steps to investigate:

• Filtered search UI components
• GraphQL?
• Vue-based listing
• Vue-based commit list item with progressive disclosure mechanism for commit details to retain recent performance improvements
• (...)

Task list

• (week 1) UI discovery - familiarise with the current implementation
• (week 1) Code discovery - familiarise with the current implementation
• (week 1) Map out the current data flow
• (week 2) Investigate filtered search (timebox because it’s something new)
• (week 2) Investigate progressive disclosure (infinite scroll could be 1st iteration)
• (week 2) Performance measuring (e.g. consider adding performance marks, Site speed testing)
• (week 2) Architecture planning*
  • Vue Architecture
  • Data flow
  • State management
• (week 2) Consider how the refactor will be guarded (i.e. separate route or selector guarded by FF)
• (week 3) Final review
• (week 3) Post spike outcome
• (week 3) Create Epic
• (week 3) Close the spike 🎉