Adjust and move comms subteam progress issue to templates

[aibarbetta]

What type of PR is this:

/kind documentation

What this PR does / why we need it:

Continue #2792
Create comms subteam progress issue template

Which issue(s) this PR fixes:

Closes retro item

Special notes for your reviewer:

Comms handbook TODOs that used to be in the template were moved to the "Comms handbook updates" item at the Retro board

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aibarbetta
Once this PR has been reviewed and has the lgtm label, please assign saschagrunert for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[chadmcrowell]

I really found this useful as release comms lead for v1.36. Thank you @aibarbetta !

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[aibarbetta]

/remove-lifecycle stale

[fsmunoz]

I've read it all and I can't really come up with anything to change - if anyone does, do propose something and break the LGTM, for now I think that the changes are an improvement to what exists and any further improvements can be added on top.

/lgtm