[feat] Aim revamped SDK

[alberttorosyan]

Implementation of the Aim Python SDK.

Provides clean interfaces for working with the metadata concepts, such as Container, Sequence, Object, etc.

Core components

• Module aim.sdk.core.interfaces; declaration of the interfaces (pure abstract)
• Module aim.sdk.core; implementation of Container, Sequence, Object and collections of them based on the aimrocks storage backend and TreeView abstraction
• Module aim.sdk.core.type_utils; implementation of Aim type sytem utilities
• Module aim.sdk.core.repo; implementation of a wrapper class for theaim.Repo class, with abstractions for supporting different types of Containers/Sequences.

Web APIs

• Endpoint api/objects/search; unified API for querying data from Aim (including types non-compatible with the new SDK, such as aim.Run, aim.Metric, aim.Images)
• Support for query expression and query object type selection.
• cURL & JS request examples:

curl --location --request GET 'http://127.0.0.1:43800/api/objects/search?type_=Sequence&q=sequence.name=='\''metric'\'''

var data = "";

var xhr = new XMLHttpRequest();
xhr.withCredentials = true;

xhr.addEventListener("readystatechange", function() {
  if(this.readyState === 4) {
    console.log(this.responseText);
  }
});

xhr.open("GET", "http://127.0.0.1:43800/api/objects/search?type_=Sequence&q=sequence.name=='metric'");

xhr.send(data);

[mihran113]

some comments/thoughts for discussion later on, overall looks great!

[mihran113]

Probably should have been a key error?

[mihran113]

In general does it make sense to do some write operations on a __getitem__ method? Aren't there any alternatives to this design?

[mihran113]

Do we want to allow filtering at all on a limited collection?

[mihran113]

Let's add also step/track call counts here as well

[mihran113]

Let's add some logic for per type sequence count to use later for stats

[alberttorosyan]

resolves #2689