Allow files to be locked in a remote project

What is the feature you'd like to have?
I just got done analyzing a few fairly large binaries and have saved the initial BNDB to a remote project, I really want to make sure that no one accidentally pushes to that BNDB.

Is your feature request related to a problem?
When collaborating with others it's hard to convey that a database is suppose to be read only.

It would also be nice if certain users can be allowed to always write to a locked database. One example use case might be having a service that reanalyzes all locked databases on a new version of Binary Ninja, this would require a user to be able to programmatically update the lock, I guess all users with write access to a project would fall into this category.

The "lock flag" for a file might also be shared for "trashed" files.

No files, tests, or entry points are named. Start by locating the remote project file and permission APIs, then define how a lock flag applies to files, trashed files, and users allowed to update locked databases. Done means the lock prevents unauthorized writes while permitted users or services can still update the database.