EPIC Goal

What are we trying to solve here?

Ensure metadata values like "support:production" or   "support:tech-preview" are exposed in scaffolder actions (/create/actions page) so software template authors can decide which actions they should use to produce prod ready STs

Background/Feature Origin

Currently, you can't tell if the the installed actions are intended for prod or TP use without consulting our docs. 

Why is this important?{}

We should surface this information in the tool in order to inform consumers so they can assume the risks of using something that is not meant for prod.  

User Scenarios

Dependencies (internal and external)

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>