ci: Setup gitflow process

[mydea]

This PR (WIP) sets up some Gitflow processes.

Some requirements that need to be done in order for this to work/make sense:

• Extend all branch protection settings we have for master to develop (so have them for both branches)
• Make develop the default branch in Github
• Either make sure that approval of the "github-actions" bot user is OK to merge a PR, or we need to provide a github token of a user in whose name the approvals will be in

How it should work (overview)

• We develop on the new develop branch. Any PRs are merged into develop
• When we want to do a release, we merge develop into master and trigger a release from there.
• While a release is pending, PRs can still be merged into develop (they will just not go into the ongoing release anymore)

How to do a release going forward?

• Create a meta changelog PR to develop (as before)
• When this is merged, we'll automatically create a PR from develop->master, auto-approve it, and automerge it when CI passed
• Trigger a release from master branch (as before)
• When this is merged, we'll automatically create a PR from master->develop, auto-approve it, and automerge it when CI passed
• Now everything should be in sync again!

Potential streamlining/improvement?

One way in which this could be improved, is to auto-trigger the release whenever we merge into master.
In order to do this, we'll need to somehow know at this point:

• the version to release
• force if there are release blockers (optional)

We may be able to parse this somehow, but I'd say this is an area for future improvement, if we decide so.

What's missing?

We'll probably have to tweak caching etc. settings a bit to streamline this - e.g. what needs to run when merging develop-> master, what needs to run when merging master->develop, etc.

[github-actions]

size-limit report 📦

Path	Size
@sentry/browser - ES5 CDN Bundle (gzipped + minified)	19.87 KB (added)
@sentry/browser - ES5 CDN Bundle (minified)	61.57 KB (added)
@sentry/browser - ES6 CDN Bundle (gzipped + minified)	18.54 KB (added)
@sentry/browser - ES6 CDN Bundle (minified)	54.88 KB (added)
@sentry/browser - Webpack (gzipped + minified)	20.29 KB (added)
@sentry/browser - Webpack (minified)	66.37 KB (added)
@sentry/react - Webpack (gzipped + minified)	20.31 KB (added)
@sentry/nextjs Client - Webpack (gzipped + minified)	47.6 KB (added)
@sentry/browser + @sentry/tracing - ES5 CDN Bundle (gzipped + minified)	26.79 KB (added)
@sentry/browser + @sentry/tracing - ES6 CDN Bundle (gzipped + minified)	25.08 KB (added)
@sentry/replay ES6 CDN Bundle (gzipped + minified)	44.15 KB (added)
@sentry/replay - Webpack (gzipped + minified)	38.9 KB (added)
@sentry/browser + @sentry/tracing + @sentry/replay - ES6 CDN Bundle (gzipped + minified)	61.5 KB (added)

[Lms24]

Seems like a good workflow to me!

Also, great diagram! Once we all agree on this, let's make sure to document this flow in our docs directory and maybe link to it from CONTRIBUTING or similar?

[mydea]

Added docs here: https://github.com/getsentry/sentry-javascript/blob/fn/gitflow/CONTRIBUTING.md

Note: I took this opportunity and extracted the publishing stuff out as well.

[Lms24]

LGTM. I like the automatic approach master/develop syncing approach and I think going forward, moving to gitflow will solve our release blocking/multiple teams working on the repo problem. Thanks for updating documentation, I think it makes a lot of sense now.

[mydea]

FYI I updated this slightly:

1. Added the gitflow image to the docs
2. Made it so we can manually trigger a sync between develop/master via GHA workflow_dispatch