Decouple sync and release actions

[viren-nadkarni]

Background

Moto-Ext current has an action that rebases the codebase with upstream repo and publishes the build to PyPI, introduced in #78.

Changes

Following the hard fork (see #83), Moto-Ext will not be rebased with the upstream repo. This PR therefore reworks this CI pipeline and splits it into two separate workflows:

• Sync moto-ext with upstream: will be able to do the rebasing only. This action will be disabled and exist only for posterity.
• Release moto-ext: will increment the micro semver, create a release and publish to PyPI.

Tests

Successful dry runs for:

• Sync moto-ext with upstream: https://github.com/localstack/moto/actions/runs/21477100477/job/61863753872
• Release moto-ext: https://github.com/localstack/moto/actions/runs/21476950500/job/61863256226

Related

Closes: PNX-558

[alexrashed]

Thanks for jumping on this! Great to see the sync being decoupled to support the future strategy. I only added a few small questions, mostly because I might not fully understand how the release cycles and the upgrade path of LocalStack is going to look like in the future... 😅

[alexrashed]

question: given that we do not have a schedule on the "sync" workflow anymore, does it make sense to have a weekly schedule on this one? Hopefully there won't be any commits in the repo in most weeks? Wouldn't this pipeline fail now if there are no commits fora whole week?
Or are there automated changes similar to #86 created by new automations strictly every single week?

[alexrashed]

question: How is this version determined and what do we expect the next few version numbers to look like?

[alexrashed]

question: Does it make sense to even keep this pipeline? You mentioned in the description that there is no plan to sync the fork with upstream anymore? If this is the case, I guess we could just remove this part / this workflow?

[alexrashed]

nit: Might make sense to rename the workflows a bit. They don't have much to do with Continuous Integration anymore I guess 😅