Steps:

1. Add/update or delete secrets in UI.
2. Make some secret changes in local.
3. User runs "npx dotenv-vault@latest push" command.

Expected:
User should get a warning that there a new changes in CI and they should copy/store their local changes somewhere and do a "npx dotenv-vault@latest pull" first.

This is since .env files are not git committed and thus we cannot use git tools for merge/etc. Of course if there is a smarter way to get some stage/resolve merge conflicts etc that would be great but am not sure how this can work when these files are ignored.

Actual:
Local changes will overwrite any changes pushed by other users in UI. Conversely, if they do a pull first, their own changes will be overwritten.