feat: add generic action to task

[lstocchi]

What does this PR do?

It adds a new property to a task to implement a custom behavior like show an 'open folder' action.
This will be used with the export container action. When the export is executing/has been executed the user could open the taskmanager, click on the open folder link to open the directory where the container content will be saved

Screenshot / video of UI

N/A

What issues does this PR fix or reference?

it is part of #6355

How to test this PR?

1. run test

• Tests are covering the bug fix or the new feature

[deboer-tim]

I'm finding it hard to follow the comments and changes afterwards, but if this went from a 'folder URI' to a function -which could do anything - why keep the property named 'folder'? Wouldn't it make sense to allow things like 'open file' or 'open logs' as well? Maybe even 'open browser'? Those seem just as likely for other tasks, and would only require a label as well.

[lstocchi]

I'm finding it hard to follow the comments and changes afterwards, but if this went from a 'folder URI' to a function -which could do anything - why keep the property named 'folder'? Wouldn't it make sense to allow things like 'open file' or 'open logs' as well? Maybe even 'open browser'? Those seem just as likely for other tasks, and would only require a label as well.

It was always a function, the thing discussed was how to pass the info ( as a string or as a Uri) to the backend.
BTW yes, it could be used for anything. But the same for the goToTask.
So you would suggest to have something generic like action: { title, function }, so that the title is the text displayed and function is the one executed when clicking?

[deboer-tim]

I'm finding it hard to follow the comments and changes afterwards, but if this went from a 'folder URI' to a function -which could do anything - why keep the property named 'folder'? Wouldn't it make sense to allow things like 'open file' or 'open logs' as well? Maybe even 'open browser'? Those seem just as likely for other tasks, and would only require a label as well.

It was always a function, the thing discussed was how to pass the info ( as a string or as a Uri) to the backend. BTW yes, it could be used for anything. But the same for the goToTask. So you would suggest to have something generic like action: { title, function }, so that the title is the text displayed and function is the one executed when clicking?

Yes, I think that's what I'm suggesting. Maybe it is even worth replacing goToTask (not necessarily in this PR...) or allowing more than one. We should keep some consistency in the labels, but this gives any task a simple and generic way to link to relevant things, whether it's a status page, logs, a folder, help, etc.

[lstocchi]

@deboer-tim updated 👍

[deboer-tim]

Thanks for the change. 👍🏼

[jeffmaury]

LGTM