Rework Blazor table filters

[alexnoddings]

Table filters initial implementation was fine for the initial requirements. However, new requirements aren't (easily) compatible with the original design.

Table filters need reworking to support new usages:

• Default values
  • These should be capable of blocking table loading while they load
• Filter logic should be separated from rendering
  • Filtering/UI are currently both provided in each component
  • This means multiple filters for one property need to track the value on their own, and need to communicate updates between them
  • Separating these makes syncing much easier as one value is stored centrally, and the UIs just show these
  • Once separate, both value stores and their UIs will be easier to implement as the inheritance currently is ugly
  • This should also unlock better support for persisting values
  • It should also unlock more scenarios for loading values, e.g. through the child content
  • It may also allow for @bind-ing

[alexnoddings]

Persisting the table state (ordering, page number) would be a nice-to-have, but may come after a first version.