impl rust Collaboration and Remote API

[rbran]

Unimplemented and other notes:

• BNRemoteFileDownload - Returns the c++ std::vector from the core API, but don't provide any way to free it.
• BNCollaborationSnapshotDownloadSnapshotFile - Returns the c++ std::vector from the core API, but don't provide any way to free it.
• BNRemoteRequest - Parameters are complex c++ types, and no direct way to manage it.
• BNAnalysisMergeConflictGetPathItem - Implementation with downcast to u64 is unclear.
• Remote::connect - Not fully implemented because it depends on enterprise and SecretsProvider.
• Remote - Methods in python preemptively calls pull_files/pull_folders/pull_user_permissions/open, but C++ don't. Python was followed.
• RemoteProject::upload_new_file - Was ported from remotebrowser.cpp, this file is not public, so I decided not to implement it.

[emesare]

I got through 18 before I realized how large this PR is.

For actual failures like merge_database a Result type would be nice, however in the absence of an actual error type it is a code smell. If you added just a simple MergeFailed type and attached it I think that would be better. This is pretty subjective so I'm sure others will have differing opinions.

[rbran]

It's probably better to leave Result<T, ()> for now, because it's very likely that an Error type will be implemented and it will be replaced byResult<T, BnError> .

Although it's not ideal, it's the current API behavior:

binaryninja-api/rust/src/metadata.rs

Line 284 in 04b58f9

pub fn push(&self, value: &Metadata) -> Result<(), ()> {