Hide deprecated features by default

[paulgrainger85]

Next Steps

We will:

• not show deprecated plugins in the Editor's autocompletion (will be complex)
• we will also filter them out in the Topology view
• for both Editor and low-code Topology forms, we need to hide deprecated properties like runner for script tasks
• for the /ui/plugins, Hide all deprecated plugins in the Plugins UI #4526 (comment)
• for the website also see issue above -- users can still find documentation for deprecated plugins from the built-in documentation in the Editor in the UI
• for Blueprints, we soon will have versioned blueprints to ensure deprecated functionality is not shown

Extra info: for deprecation of larger features, we can continue using enabled configuration allowing users who need it to enable it until transition https://kestra.io/docs/configuration-guide/enabled

Feature description

In views like Topology and Plugins, we show deprecated features. It can be unclear to end users whether functionality is still supported when they use them in this way.

Instead, we should hide these plugins by default, e.g. take topology for example, the first 3 items are deprecated

Instead of showing these, we should hide them. However, users should still be able to find them if needed -- possible options to consider:

• a configuration explicitly enabling deprecated plugins
• a UI toggle which will display the deprecated plugins

Tasks

Preview Give feedback

1. Hide deprecated core Python, Node + Bash script plugins in the no-code Editor form #7205
   area/frontend bug +2
   
2. Hide deprecated core Python, Node + Bash script plugins in autocompletion #7206
   area/frontend bug +2
   
3. Add group for deprecated properties in the no-code Editor #7207
   area/backend area/frontend enhancement +3
4. Group core task properties into "Core properties" section #7199
   area/backend enhancement +2
   

[MilosPaunovic]

I believe this need to be handled on the BE side.