Update issue template and add workflow to automatically close talk issues

[da5nsy]

Following this comment this PR adds the workflow.

It also makes a minor update to the form template.

[da5nsy]

Converted to draft because I realised that in the current form close-talk-issues.yml won't do the bits that relate to adding new bits to a newsletter issue, as that is no longer in the same repo (the target issue is currently here but while we're changing it maybe it would make sense to change that target to the newsletter repo instead).

@aleesteele do you have a preference on whether that issue is autogenerated on the main repo vs the newsletter repo?

@the-turing-way/infrastructure-working-group - is it as simple as changing lines 127/148/158 on this file to the desired target repo? Is there any permissions required to allow a bot to post onto a different repo than the one it's coming from? What format does the repo string need to be in if we're hard-coding it?

[bsipocz]

I'm fairly certain you can trigger issues opened in a different repo, after all we're all in the same org, and the repos are public, anyone can open issues.

However, I think Anne should comment on it first if this feature is any helpful or not to begin with.

[da5nsy]

I'm fairly certain you can trigger issues opened in a different repo, after all we're all in the same org, and the repos are public, anyone can open issues.

@bsipocz - do you know what format the repo parameter would need to be in, or how we'd find out without just using trial and error?

[da5nsy]

However, I think Anne should comment on it first if this feature is any helpful or not to begin with.

Hi @aleesteele - is the feature of automatically adding talks to a newsletter issue useful?
If it is, we'll work out how to make it work, if not we will scrap it.