Feat(issues_grid_view): add issuable grid view component feature

What does this MR do and why?

Related issue: #323095 , #387022(MVC1)

Related JH issue: https://jihulab.com/gitlab-cn/gitlab/-/issues/2150

These MRs implements MVC1 described in this #387022. It revamps the issue page by adding a grid view (while keeping the list view) for both group and project issues. Users can customize the order of fields in the grid view and add or remove fields (with "id" and "title" being fixed fields), and their customization config is cached in the browser.

This is the second MR split from the original MR : !113012 (closed)

In this MR, we will add the grid view function (it was empty in the previous MR), where the header configuration of the grid view is stored in a variable, which is convenient for the next MR to customize the header function.

This feature is controlled by the feature flag issues_grid_view

MRs:

1. Add feature flag, add tabs and add empty grid view div: !120211 (merged) .
2. Current MR, Implement the gridView function (We can see grid view now).
3. Add issue field drawer component, we can customize the grid header now.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

1. Open the feature flag issues_grid_view in rails console. (::Feature.enable(:issues_grid_view))
2. Go to the issue page of any group or project.
3. Click 'grid', observe.

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.