Update keys for v0.28.0

[bidoubiwa]

Changes related to the keys management

Related to:

• issue: Pagination of the /keys ressources meilisearch#2442
• issue: Change of the API key resource meilisearch#2369

All the changes:

• Creation of client.get_keys_with() that lets you paginate on limit (default: 20), offset (default: 0).
• The returned keys when using get_keys_with get_keys or get_key now returns an additional field uid.
• get_key, delete_key and update_key accepts both the uid or the key itself as a selector
• create_key accepts a custom uid to generate a determinist API key. If null Meilisearch generates one. It must be a UUID v4 value.
• create_key accepts a custom name.
• update_key only accepts updates on the description and the name
• The response from get_keys_with and get_keys is now a KeysResults instead of Vec<Key>.

Breaking

• The returned keys when using get_keys_with get_keys or get_key now returns an additional field uid.
• The response from get_keys_with and get_keys is now a KeysResults instead of Vec<Key>.

get_keys without filtering

    let client = Client::new(MEILISEARCH_HOST, MEILISEARCH_API_KEY);
    let keys = client.get_keys().await.unwrap();

get_keys with filtering

    let client = Client::new(MEILISEARCH_HOST, MEILISEARCH_API_KEY);
    let mut query = KeysQuery::new();
    query.with_limit(1);
    let keys = client.get_keys_with(&query).await.unwrap();

Response:

pub struct KeysResults {
    pub results: Vec<Key>,
    pub limit: u32,
    pub offset: u32,
}

[alallema]

Well Done! I really like the new way to handle the key 🏅
I just have some questions

[alallema]

I don't see where you made a copy or use Clone?

[bidoubiwa]

Its to give the possibility to the user to copy if they'd like to

[irevoire]

I have a lot of concerns about the test; I know it probably won’t cause any issue right now but I’m afraid they’ll become flaky after some time thus, most of my comments are to prevent this from happening.