Case table improvements

[shanisagiv1]

In order to improve case management, we should adjust our main case table to support more capabilities similar to other tables we support (alerts/rules)
The following features should be implemented to align the experience with our other tables and improve the current offering for cases:

• Allow users to manage which column to show in the table
• Allow users to sort by date/numeric columns.
• Allow users to filter by the pre-defined columns(status, severity, assignee, tags, category) and allow multi-value selection for all fields even status or severity.
• Persist the table view with customization for future usage per user (based on browser storage)

out of scope:

• Implement KQL in the search bar
• Have more details that highlight the important details from a case (#alerts,#attchemnts, etc) - TBD to research which ones are the most "used"

ERs:

• https://github.com/elastic/enhancements/issues/18773
• https://github.com/elastic/enhancements/issues/18592

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[cnasikas]

Thanks, @shanisagiv1.

Allow users to sort by all the available columns.

Unfortunately, it is not possible to sort all available columns. For example, you cannot sort by the total number of alerts or the "External Incident" column

Allow users to filter by the pre-defined columns

Which are the pre-defined columns?

Also, I think we should persist the user's configuration at the local storage.

[shanisagiv1]

Thanks. updated to desc.

Also, I think we should persist the user's configuration at the local storage.

what does this mean? @cnasikas

[shanisagiv1]

@mdefazio cc

[cnasikas]

It mean that if the user refreshes the browser her configuration will be kept.

[cnasikas]

Implemented by #172276 and #170950 for 8.12.