ci(release_workspace): add additional checks and document workflow

[BethGriggs]

• Refactored the workflow to infer the branch from the workspace name using the pattern workspace/${workspace}
• Removed the unused branch input from the workflow
• Added handling for missing GitHub events in release checks
• Introduced logic to set npm publish tag (latest or maintenance)
• Added initial plugin maintainer guide for patching older release lines

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

• [ ] A changeset describing the change and affected packages. (more info)
• [x] Added or updated documentation
• [ ] Tests for new functionality and regression tests for bug fixes
• [ ] Screenshots attached (for UI changes)
• [x] All your commits have a Signed-off-by line in the message. (more info)

[BethGriggs]

During the SIG today we discussed some various improvements and further prototyping needed here, I'll work on those

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[BethGriggs]

This is still needed, I just need to find time to update based on latest flow suggestions

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[BethGriggs]

Plan to pick this up again now I am back from vacation

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[github-actions[bot]]

This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!

[BethGriggs]

@awanlin, it's more an alternative approach - I'd rather leave this open until we have some feedback on https://github.com/backstage/community-plugins/pull/2626

[awanlin]

Ah, thanks for the context, I'm fine with that then 👍

[BethGriggs]

Now superseded by https://github.com/backstage/community-plugins/pull/2626, for a summary of where we are see https://github.com/backstage/community-plugins/issues/860#issuecomment-2689545426