Hide all deprecated plugins in the Plugins UI

[anna-geller]

Describe the issue

See https://share.descript.com/view/bpmC3CeMXRP :)

Environment

• Kestra Version:
• Operating System (OS/Docker/Kubernetes):
• Java Version (if you don't run kestra in Docker):

[loicmathieu]

It's because we open the first in the list, not sure we can do anything about it at this stage.

Or we may change to open a plugin group page with a list of plugins instead of going to the first one.

[anna-geller]

We should find a way to hide all deprecated plugins from the Plugins page in the UI and website. On the website, we asked Taron kestra-io/docs#1626

[loicmathieu]

On the UI it's a bit more problematic as if a user uses a deprecated task, he still needs to be able to access its documentation.

[anna-geller]

Documentation is still available.

Here is my thinking, you can say whether you agree:

1. If a user already uses a deprecated plugin in their flow, they can access the documentation within the Editor or from the docs on the website (see the image below)
2. If a user explores plugins via the Plugins UI, they should only see active plugins (deprecated plugins shouldn't be shown)

agree?

[brian-mulier-p]

To handle it we would have to duplicate the API call to retrieve plugins without deprecated tasks for this home page, not sure we want to do that considering the issue which is really minor imo 🤔

[anna-geller]

Discussed today: let's add a filter to remove deprecated plugins and not show them both on the website kestra.io/plugins and on the UI /ui/plugins/ (in the UI: direct access like https://preview-oss.kestra.io/ui/plugins/io.kestra.plugin.core.debug.Echo will still work)