Feature: FlowList and DeploymentList components

[znicholasbrown]

This PR:

New:

• FlowList component; functionally equivalent to the FlowsTable
• FlowListItem component; functionally equivalent to a row in the FlowTable except contains a list of its deployments, used in FlowList
• DeploymentList component; functionally equivalent to the DeploymentsTable, used in FlowListItem
• DeploymentListItem component, functionally equivalent to a row in the DeploymentsTable, used in FlowListItemDeployments
• lastFlowRun composition; creates a subscription for the most recent flow run (by expected start time) matching the passed filter and returns a ComputedRef for the run and the subscription itself
• nextFlowRun composition; creates a subscription for the next flow run (by expected start time) matching the passed filter and returns a ComputedRef for the run and the subscription itself

Enhanced:

• deployment, flow, and flow run mock APIs all support basic filtering and sorting
• StateListItem component now supports an action slot, along with several other enhancements (non-breaking, should all be purely additive)

Fixed:

• mock data store utilities are now properly hydrating date objects for flows, deployments, and flow runs and schedule objects from deployments

[znicholasbrown]

@brandonreid fixed the border radius issue; I'm not against an icon per-se but I also don't want to shoe-horn them into this design when we're not using them for top-level items anywhere else.

[znicholasbrown]

Also this PR is missing commits atm cause of the ongoing github issues - some of the fixes won't yet be applied

[znicholasbrown]

Ok looks like all commits are showing up and should be in the demo now

[pleek91]

Sorry for so many comments. There's a lot here that's really good. And I love the direction. Just wanting to really iron this out since its a significant rewrite.

[znicholasbrown]

So I went ahead and wrote useDeployments, useDeploymentsCount, useFlowsCount compositions and modified the existing useFlows composition to add a new overload for passing flow ids or a flows filter; lmk what you think of that implementation. The one caveat is that I retained permissions checks in the filter the composition uses, which means that technically every component will still need to do objectList ?? [] because there's a chance a user is missing permissions and the subscription never runs, according to the UseEntitySubscription overload. We could relax that type a bit but I think it makes sense as a generic and the undefined return might be a useful indicator.

All other feedback has also been addressed 😄

[pleek91]

LGTM. Thanks for working through all the details with me!