[Plugins markdown redesign] Improve the design of the plugin documentation with expandable/collapsible properties display

[anna-geller]

Goals

1. More compact display of properties to avoid overwhelm
2. Provide full examples related to any given properties directly within that property description rather than at the top (requested by a user here Examples displaying in documentation #4226)

Feature description

1. The type and default need to remain as is = prominently displayed. In contrast, required and dynamic (or not) can be just an icon
2. Expand + collapse properties, outputs and metrics with collapsed by default
3. Expand + collapse for each single property (property description, type and default value) - the icons can be displayed directly
4. Redesign a "homepage" of each plugin

Example property as of today

• Type: boolean
• Dynamic: ❌
• Required: ❌
• Default: false

[wrussell1999]

Table of content to make it easy to see all available properties etc. Not available in Kestra. Only on the website, e.g: https://kestra.io/plugins/core/tasks/http/io.kestra.plugin.core.http.request

[wrussell1999]

Making sure the custom types are obviously clickable and link to their specific section.

[anna-geller]

• for required properties
  then ⚙️ for configurable/dynamic

[anna-geller]

Note to self: discuss with Nico when he's back to extend this figma design https://www.figma.com/design/g8Di3M1gbajOjOqp0ZrzXO/02_Kestra.io?node-id=10976-88344&t=XQemhHC3x27UJPE8-1:

1. Move deprecated properties into a separate section e.g. Python script now has multiple deprecated properties like runner, docker, outputDir - distracting to new users, unpleasant to existing ones
2. Detailed Table of contents in the right sidebar for all Properties, Examples, Outputs
3. Allow providing examples for specific properties e.g. in the Python example you use, we could offer 2 full examples of how to use Python task with Docker and AWS Batch task runners, but this example would need to be under the taskRunner property rather than in the main examples -- this was requested by the community Examples displaying in documentation #4226
4. For default values, I'd prefer to show it more prominently, perhaps in a grey color right before the type?
5. We are missing an example of a clickable definition. in python plugin, NamespaceFiles is a clickable definition, it would be nice to perhaps show it as a hyperlink?