Adjust the v1 of the github-actions package to be deprecated

[eason9487]

Changes proposed in this Pull Request:

Part of #108

This PR:

• Mark the v1 of the github-actions package deprecated.
• Change the PR merge base in the release workflow to source/actions-v1 branch

Detailed test instructions:

This PR involves the release processing of the github-actions package. It can only be verified after merging it to source/actions-v1. Therefore, I tested it with a forked repo.

1. View the merged commit that has the same commit as this PR.
   • eason9487@644585e
2. View the workflow that prepares the PR for releasing version 1.11.3.
   • https://github.com/eason9487/grow/actions/runs/8847453520
   • Release version 1.11.3 of the github-actions package eason9487/grow#33
   • The merge base is source/actions-v1
     
3. View the workflow that publish the new release after approving the release PR.
   • https://github.com/eason9487/grow/actions/runs/8847468906
   • https://github.com/eason9487/grow/releases/tag/actions-v1.11.3
4. View the workflow that creates the build for v1.11.3 and updates tags.
   • https://github.com/eason9487/grow/actions/runs/8847471464
5. View the Tags page. The actions-v1, actions-v1.11, and actions-v1.11.3 tags were created and pointed to the same revision.
   • https://github.com/eason9487/grow/tags
     
6. Read the updated README to see if it is clear enough.

[tomalec]

Read the updated README to see if it is clear enough.

After the changes from this PR the packages/github-actions/README.md will not cover releasing a new major version.
For the upcoming v2 version, do you plan to remove the changes to README.md from this PR? Leaving 1.x.y patch release instruction only at source/actions-v1? Would you stack them so that for v2, we'll see both ways? Or is the plan to remove major release instructions completely, as they are more complicated?

Or is the idea to keep source/actions-v1 branch away from trunk?

[tomalec]

Reviewed the code, checked readmes and workflow runs.

LGTM Assuming, I understood correctly the release process split, and we'll keep source/actions-v1 as a separate branch & not plan to merge it into trunk

[eason9487]

Hi @tomalec, thanks for the review!

Or is the idea to keep source/actions-v1 branch away from trunk?

Assuming, I understood correctly the release process split, and we'll keep source/actions-v1 as a separate branch & not plan to merge it into trunk

Yes! I set the source/actions-v1 as a protected branch and it will be kept and not be merged into trunk.