Default save behavior to always include local store
Currently you can opt to save your datapackage changes to either LOCAL, NETWORK, or BOTH. This means you can make changes to a package then opt to save them only to the NETWORK. This can leave your local store a version behind and I don't undersand the usecase for that.
I am proposing that we always save changes locally (if local does not already have the latest version).
I started thinking about this because of a related bug that displayed different local and network revisions simultaneously (#5805). I think we should still try to address that bug, but I'm not exactly sure how to guarantee it will not continue to be a problem especially if we maintain distinct revision histories for local and network content. (This may qualify as yet another bug for discussion).