Update Applications Table

[joepavitt]

Description

Correct me if this isn't the branch to be PRing back into @Pezmc. This also includes a merge of main so I could get the other UI work I'd done, hence the ridiculous number of files changed and commits, not sure how best to coordinate branches here, I can continue to pull updates from your feat-1735-expose-applications branch and then this PR could be the primary merge to main?

Updates:

• Remove Team > Overview Page
• Rework Applications table to show nested Instances

Still to do:

• Update E2E Tests
• Possible change of layout of table (see comments below)
• Cannot render the "Open Editor" button as that is currently missing from the instances list for the /applications/<application-id>/instances API endpoint.

Related Issue(s)

Closes #1851

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass

[joepavitt]

First pass, in order to align with the design resented here:

This doesn't look very good when it's just a 1:1 Application > Instance, although I don't mind how it is in the design linked.

As such, going to iterate on this to the below, first mentioned here

[joepavitt]

Dev'd up the alternative view, it uses up a lot more vertical space, but think it breaks down the hierarchy better. This is quite an unlikely scenario, where they have 6 different applications, and only one instance in each, vertical space is used more effectively for multiple instance within a given application due to where the padding lives.

In both scenarios, the duplication of Instance/Application name makes it trickier to digest too

Screen.Recording.2023-03-30.at.18.28.45.mov

[Pezmc]

In both scenarios, the duplication of Instance/Application name makes it trickier to digest too

This shouldn't apply any more, create new instances in your applications and delete the ones with the duplicate names (and/or create new applications).

[joepavitt]

This shouldn't apply any more, create new instances in your applications and delete the ones with the duplicate names (and/or create new applications).

Appreciate that - didn;t see an API (exposed in the application.js service) to update name of an existing Application? If there is an API for it, I'll just add the function to the service and functionality into UI

[Pezmc]

Renaming is not available yet, create new ones! The API is there for it though, see the application route on the backend.

It's set as a follow up on #1735

[joepavitt]

If the API is there (I'll go digging in a second) - I'll just add it front-end - 10 mins of work.

[joepavitt]

All development work now done - just tests remaining which I will get to next week (Tuesday)

[Pezmc]

@joepavitt after the other branches merged to main, I will do a rebase and then review this branch

[joepavitt]

This has a merge from main and regular merge from your branch that this merges to. A lot of the difference here will come from the diff between main and your branch, so may be worth pulling latest main into yours to get the correct difference here?

Alternatively, we can switch this PR to point to main and merge your PR independently (and first)

[Pezmc]

Addressed my comments since Joe is out