Changes related to the next Meilisearch release (v1.9.0)

[meili-bot]

Related to this issue: https://github.com/meilisearch/integration-guides/issues/301

This PR:

• gathers the changes related to the next Meilisearch release (v1.9.0) so that this package is ready when the official release is out.
• should pass the tests against the latest pre-release of Meilisearch.
• might eventually contain test failures until the Meilisearch v1.9.0 is out.

⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.9.0) is out.

This PR is auto-generated for the pre-release week purpose.

[curquiza]

The purpose here is to update the tests to make it work with v1.9

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.62%. Comparing base (0131c58) to head (12d4678).

:exclamation: Current head 12d4678 differs from pull request most recent head 6aa0623

Please upload reports for the commit 6aa0623 to get more accurate results.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #535 +/- ## ======================================= Coverage 86.62% 86.62% ======================================= Files 10 10 Lines 1600 1600 ======================================= Hits 1386 1386 Misses 116 116 Partials 98 98 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[curquiza]

I added the retrieveVector parameter to ease the test part

[curquiza]

Putting breaking changes because the hybrid changes on Meilisearch are breaking, so I want to inform the users, even if it's not breaking on the go SDK side

[meili-bors[bot]]

Build succeeded:

• integration-tests (go current version)
• integration-tests (go latest version)
• linter