Rename develop to main; remove master

[lossyrob]

The PySTAC release route through branches should got develop -> master -> release branch -> tag. As seen in #279, the merge into master often gets skipped because it's not utilized nor valuable IMO.

I suggest renaming develop to main, and removing master, so that the new release route would go:

• PRs go into main
• Release merge main into the release branch
• Release branch is tagged for the final release.

[matthewhanson]

This does seem to be the preferred way I see repos moving to. I've gotten so used to the whole develop branch, then master as the last release, but have come to realize as you said, it doesn't seem to offer much benefit, since releases are tagged anyway.

What is the purpose of the release branch though over just tagging main? It looks like there is a branch for each minor release, is that to make backports easier?

[lossyrob]

Exactly, in especially since PySTAC is tied to producing specific STAC versions, if there's a fix we want to backport to an earlier release to make it work with users who are producing an earlier version of STAC, backporting becomes more straightforward.

[lossyrob]

Note: We are doing this now. If something is broken because of this change, please let us know!

[duckontheweb]

@lossyrob Looks like the CI didn't catch up to the branch name change, I can fix that in a PR.

[lossyrob]

Ah, yep that would be good!