Use recommended release strategy about setup-python

[bryanmacfarlane]

We're not doing this anymore. We're moving toward ncc. See javascript-action PRs from me and talk to Josh

[konradpabjan]

A releases branch, release/v1 has been created to track of a stable release version. The v1 tag has also been adjusted to now point to that branch. In the future if there are big changes then releases/v2 etc. will be created along with new tags. The master branch will remain functional with the latest and greatest changes changes. After changes in the master branch are validated and confirmed to be working they will be ported over to the releases branch.

Node_modules have been removed from the master and release branch and we now rely on ncc to create a single js file for release. Since the master branch will continue to function, there is no need for deprecation warnings or error messages. We document that using a reference to the master branch could cause breaking changes in the future so no further action is needed: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsuses

[bryanmacfarlane]

At that point it's just code and branches and the branching is up to you.