🛠️ Ansible assets in Releases should have clearer names

[beforan]

Summary

Currently in the Publish and Release workflows the artifact for the Ansible playbooks is not named very clearly.

It should be clearer that it contains Ansible related files, and should be named consistently between the artifact and the asset.

Tasks

• Rename the Ansible artifact uploaded by the Publish workflow
• Add the Ansible asset to the Release body

Acceptance Criteria

• Publish workflow runs upload the artifact with a name identifying it as Ansible related
• Releases contain reference to the Ansible asset in the body text
• Releases include a suitably named asset for Ansible
• Docs refer by name to the Ansible asset
• Legacy releases contain a consistently named asset, if present.