[UI] Refactor Outputs to gradually expand/collapse nested outputs

[vivane]

Refactor outputs:

Feature description

Execution outputs for structured objects are shown as one property per line. With large data, screen becomes hard to read. For example:	Task	Value	Name	Output
task-1		objects.0.key	file.txt
task-1		objects.0.size	123
task-1		objects.0.owner.id	456
task-1		objects.0.owner.displayName	user

It might be more user-friendly, if structured data will be shown expandable/collapsible:	Task	Value	Name	Output
task-1		objects	[...] +

...when user expands the array...	Task	Value	Name	Output
task-1		objects	[...] -
		objects.0	{...} +

...when use expands the object in the array...	Task	Value	Name	Output
task-1		objects	[...] -
		objects.0	{...} -
		objects.0.key	file.txt
		objects.0.size	123
		objects.0.owner	{...} -

...when use expands the object in the object...	Task	Value	Name	Output
task-1		objects	[...] -
		objects.0	{...} -
		objects.0.key	file.txt
		objects.0.size	123
		objects.0.owner	{...} -
		objects.0.owner.id	456
		objects.0.owner.displayName	user

[vivane]

Also:

• Tasks themselves might be expandable/collapsible.
• Table columns might be resizable.

[Nico-Kestra]

Hello, maybe this will save us a meeting. Here is a first draft for the Outputs page, thought out with Ludo last Friday. We're using the same UX as on: https://jsonhero.io/j/q01i3ytnKWRu

Figma link

[anna-geller]

https://www.figma.com/design/ew0uXk0NRXJ2NBBJTNe2n1/01_UI?node-id=1816%3A11597&t=Zzl8ZcEB22zNIGMx-1

[anna-geller]

@Nico-Kestra we need to find a way to implement a similar output handling for Trigger variables

[anna-geller]

Great job, @MilosPaunovic! closing as the main scope is done and working well