Add sensible default gitbutler behavior for common git actions in non-git-butler clients

[wesharper]

One of the barriers for my team's adoption is subtle misuse of the tool due to "muscle memory" with other git workflows. This commonly results in team members creating new local branches, committing to gitbuter/integration directly, etc.

In a perfect world, gitbutler would have sensible default behavior when one of these actions occurs.

For instance, if a user commits to gitbutler/integration directly, gitbutler could automatically apply those commits to the selected default virtual branch.

Or, if a user checks out a different branch, git butler could fall-back to a different mode and behave like a traditional git client with warnings that it's not the intended workflow and a button to change to the gitbutler/integration branch and move commits and in-progress changes to a gitbutler virtual branch.

Additionally, the specific behaviors of different actions could be configurable at a user level to accommodate different preferences.

Love the product so far!