Refactoring RemoteDatabase API

[lvca]

With ArcadeDB 23.10.1, the RemoteDatabase API has 2 use cases:

• manage the server
• being a BasicDatabase implementation to emulate most of the EmbeddedDatabase API

The ideal would be splitting the class in 2:

• RemoteDatabase as only a BasicDatabase implementation that works with a remote server and
• RemoteServer, as a new class that allows to control the server, namely: create/drop databases, create/drop users, list for available databases and in the future more operations with the server. This class doesn't need the database name

This would break the current API for whom is using RemoteDatabase to manage server users, list the available databases and create new databases.

[lvca]

Completed. @gramian, I moved the server methods in the new RemoteServer class for documentation purposes.