[UI v2] feat: Adding concurrency-limit-task-run-card component

[devinvillarosa]

1. Create route placeholder for /runs/task-run/$id
2. Ports over @/utilities/seconds
3. Adds RunCard component to be used

Checklist

• This pull request references any related issue by including "closes <link to issue>"
  • If no issue exists and your change is not a small fix, please create an issue first.
• If this pull request adds new functionality, it includes unit tests that cover the changes
• If this pull request removes docs files, it includes redirect settings in mint.json.
• If this pull request adds functions or classes, it includes helpful docstrings.

Relates to #15512

[devinvillarosa]

ported over from other repo

[aaazzam]

@devinvillarosa IIRC was have "RunCards" like this all over. What's "concurrency"-y about this component?

[devinvillarosa]

@devinvillarosa IIRC was have "RunCards" like this all over. What's "concurrency"-y about this component?

ahh makes sense.
I think this may be the first one for re-platforming.

I don't mind revisiting this and make a more generic RunCard UI component to be used instead once we tackle it in another page

[devinvillarosa]

@devinvillarosa IIRC was have "RunCards" like this all over. What's "concurrency"-y about this component?

Actually, I see what you mean. I updated the component to be just RunCard where it can render for task runs or flow runs.
But the flow runs will probably need to re-visit this component when we develop the Flow Run card to add additional features like onSelect, params, etc

[desertaxle]

It'd be cool to use @faker-js/faker to generate random task runs for display. I've been doing that for deployments, and it's helped me uncover some edge cases when working with display components like this.

[devinvillarosa]

ok, I've started to centralize some reusable schemas using faker in @/storybook/utils/mocks

[desertaxle]

Task runs aren't guaranteed to have a parent flow run, so we'll need to handle this case without erroring.

[devinvillarosa]

I think I addressed this in the latest push

[desertaxle]

I think we may want to make this parentRun and run in the future to be more flexible and handle more cases, but this is good for now since it has parity with the current UI.