cI: Release Automation Step 1

[BobaFetters]

This is the first step in automating our release process as much as possible. The plan is to have this manually triggered CI job that can create the initial PR and handle all the basic tasks associated with that. Then a separate CI job that will be triggered on merge of release PRs to handle the tasks associated with that (tagging, creating release on github repo etc)

Currently planning to leave CHANGELOG handling as a manual process and get as many other parts of the CI process as possible automated and then revisit the possibility of automating CHANGELOG handling as well.

Sample Release PR created by this workflow: #394

The "Things to do as part of releasing" section will be the focus of the workflow that triggers from merging the release PR.

[netlify]

✅ Deploy Preview for eclectic-pie-88a2ba canceled.

Name	Link
🔨 Latest commit	8ea9ca4
🔍 Latest deploy log	https://app.netlify.com/sites/eclectic-pie-88a2ba/deploys/6671edc20eedf80008e16174

[netlify]

✅ Deploy Preview for apollo-ios-docc canceled.

Name	Link
🔨 Latest commit	8ea9ca4
🔍 Latest deploy log	https://app.netlify.com/sites/apollo-ios-docc/deploys/6671edc2e3f41b00084749d0

[AnthonyMDev]

This is awesome! Thanks so much for getting this started!

[calvincestari]

Currently planning to leave CHANGELOG handling as a manual process and get as many other parts of the CI process as possible automated and then revisit the possibility of automating CHANGELOG handling as well.

I think the changelog can definitely be automated but we'd need to all adopt PR titles like Conventional Commits specifies. The changelog will be less descriptive than we have now but collecting those explanations is what makes it a manual process at the moment.

[calvincestari]

but we'd need to all adopt PR titles like Conventional Commits specifies.

We could enforce this through our PR validation action so the community has to abide too.

[calvincestari]

LGTM!

[BobaFetters]

but we'd need to all adopt PR titles like Conventional Commits specifies.

We could enforce this through our PR validation action so the community has to abide too.

Yea I assumed we would do something along these lines, figured some investigation and discussion to decide exactly what we want to would be good.