Refactor ruleset details page

[zepich]

Discussed in #101

^{Originally posted by Digi92 June 23, 2023}
If a user includes larger rulesets in his project, it can quickly become cluttered in the detailed view.
Rulesets can contain many individual rules and the rules themselves can contain many items.
I think there should be some kind of pagination for both cases to keep it more clear.
I could also imagine that particularly large rulesets could generate a memory limit error while rendering the list view.

What is your opinion about this?

Changes

• Replace the list of rules and items in the ruleset details view with a table. The table has to be sortable and needs a pagination. In the table, all rules in the ruleset are listed with a button on the right side to see the content of the rules.
• When the user clicks on the button in the table, the user will see a new view with the details of the rule. This new view will also have a sortable table with pagination and lists all rule items in a rule.
• The rules table should be filterable by choosing the rule types that should be visible in the table.

Suggested by

• @Digi92