Add adaptor tags to show quality and support

Goal: Improve developer experience by indicating the level of support and quality of adaptors

KPI: Consultant NPS

When building workflows, developers do not know the level of support an adaptor gets from the core team and/or community. A poorly maintained adaptor might affect a workflow's scalability and require a workflow redesign in the future to support new use cases which might be frustrating for them.

Solution Concepts:
Give adaptors a tag: Core, New, Outdated [TBD], and add the tags to the [package.json?] for each adaptor.
On Lightning:
We want to nicely render the tags on the canvas under each job and also in the docs panel on the editor.

In the future, we would love to render the information on the adaptor docs overview and functions page.

Start by locating the adaptor package.json files and the Lightning canvas and editor docs-panel entry points. Clarify the final tag set and ownership rules, then define completion as tags being stored for each adaptor and rendered under jobs and in the editor docs panel; the future overview and functions-page work is explicitly later.