check if current user still holds the write lock when upload changes

[jiaruiz717]

iTwin/itwinjs-backlog#1170

There is a possible scenario that two users try to upload local changes to the same cloud container:

1. User1 grabs the write lock and sit there for a very long time. User1 does not release the write lock even after it has expired
2. User2 grabs the write lock after User1's write lock expires, and upload something to the cloud container
3. User1 then tries to upload changes, we should disable User1 from uploading his changes because the write lock has expired

However, if there are no other users grab the write lock after User1, we allow User1 to upload changes(and refresh the write lock) even if the write lock has expired.

Native change:
imodel-native: iTwin/imodel-native#819

[mergify]

This pull request is now in conflicts. Could you fix it @jiaruiz717? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

[mergify]

This pull request is now in conflicts. Could you fix it @jiaruiz717? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/