TT-18216: add a workflow to restore archived artifacts for support

[olamilekan000]

Description

Retention restore turns a support request for a retired version into a
workflow dispatch: given an archive key it initiates the Deep Archive
restore, and on a later run downloads the object, verifies it against
the committed plan's checksum and attaches it as a workflow artifact.
Keys not present in a committed plan are refused. Every outcome is
posted to the retention Slack channel

Jira Ticket: TT-18216

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Chore / documentation / template sync

Verification & Testing

• I have run local unit tests (go test ./policy/...) and they passed.
• I have generated policy outputs locally (go run . policy gen) and verified the rendered files.
• I have verified the changes in target downstream repositories (e.g. tyk, tyk-analytics).

Command(s) used for testing:

# Example: go run . policy gen /tmp/output --repo tyk --branch master

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[rafalgolarz]

hi @olamilekan000
Did you test it?

[olamilekan000]

hi @olamilekan000
Did you test it?

Workflow dispatch can't be tested until it's merged to default branch

[rafalgolarz]

hi @olamilekan000
Did you test it?

Workflow dispatch can't be tested until it's merged to default branch

[rafalgolarz]

sorry, accidently closed it 😁 reopened.