EPIC Goal

The goal of this is to create the QE work related to the new scaffolder action for versioning templates.

Background/Feature Origin

Today, we have the ability to set the relations between an entity that was created by a particular software template using `scaffoldedFrom` from the `@backstage-community/plugin-scaffolder-backend-module-annotator` plugin. We would like to take this a step forward and now include versioning information to the entity based on the version of the template that created it.

Why is this important?

This will allow users to be able to reference what version of a particular template they used to create their entity. This can help in identify problems and give more information about where the source of the issue might be. This also can be used as another mechanism for tracking the lifecycle of a particular template

User Scenarios

As a platform engineer, I want to be able to version software templates

As a platform engineer, I want to be able to version the catalog entities that are created using my software templates

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>