[DIR-1444] [DIR-724] [DIR-1506] migrate to new instances api

[stefan-kracht]

Description

Migrating to the v2 instance API

• The instance list endpoint does not support streaming anymore, I added a reload button to the top of the list
• instances can now also be filtered by status === crashed (the possible statuses were hard-coded in the filter component, I added a direct binding to the schema so that every new status will automatically be added to the filter)
• the streaming on the details page will now stop when the instance is not running anymore (this saves some browser resources, the streaming endpoint pushes updates very frequently, even when nothing changes)
• found a way to fix DIR-724
• I updated the API commands button on the workflow page to use the new API (this closes DIR-1506)
• I removed the api/tree folder after we migrated all APIs (the FileNameSchema is the only thing we still use, I moved that into src/api/files/schema.ts)
• The new API design fixes a major bug in the diagram on the instance page. The diagram was always generated based on the current file content of the workflow that triggered the instance. This workflow might have changed since the workflow ran, and the diagram could show something completely wrong. If the file was deleted or renamed after the instance was generated, the diagram would not have been displayed at. With the new API, the content of the workflow that created the instance will be part of the response and can be used as a reliable source for the diagram.

Follow-up tickets

To let us move a bit quicker in the API migration, I added the following task as a separate ticket as I think it is a good iteration and not a mandatory

• handle big output on the instance page

Checklist

• Documentation updated if required
• Test coverage is appropriate

Checklist Internal

• Linear issue linked (e.g. [DIR-XXXX] pull request title)
• Has the PR been labeled

[sebxian]

This looks good to me!

Some comments in the code regarding naming.

I also have one question -- this is probably outside of the scope of this PR, but for clarification: Was there a discussion with the backend guys regarding the format of the filter params? I think they could be improved, and that might also lead to a simplification of currently hard coded stuff in the ui. But that would probably be a separate issue.

[stefan-kracht]

This looks good to me!

Some comments in the code regarding naming.

I also have one question -- this is probably outside of the scope of this PR, but for clarification: Was there a discussion with the backend guys regarding the format of the filter params? I think they could be improved, and that might also lead to a simplification of currently hard coded stuff in the ui. But that would probably be a separate issue.

No, there was no discussion of changing the query parameters. Maybe we make this is a future ticket and align the params with the event filter ones.

[sebxian]

Thanks for the updates. As discussed, I pushed some more changes to get all the spelling consistent. Good idea about a follow-up for event & instances filters, I'll keep this in mind while working on the events!