[v1.14] Filterable attributes settings opt-out

[Strift]

This issue follows the changes related to Meilisearch v1.14.0 mega issue.

Description

Update the settings API to handle the new filterableAttributes syntax.

For more context, see the related issue in Meilisearch: meilisearch/meilisearch#5163

Tasks

• Update the methods to update settings to accept the new filterableAttributes syntax
• Update the methods to return the new filterableAttributes syntax (when Meilisearch returns it)
• Update update_filterable_attributes_1 code sample in .code-samples.meilisearch.yaml

For reference, here's how the test are implemented in Meilisearch JS SDK:

// this mixes the old syntax (field name) and new syntax (settings opt-in)
const newFilterableAttributes = [
  "author",
  {
    attributePatterns: ["genre"],
    features: {
      facetSearch: true,
      filter: { equality: true, comparison: false },
    },
  },
];
// we update the filterable attributes settings
await client
  .index(index.uid)
  .updateFilterableAttributes(newFilterableAttributes)
  .waitTask();
// the method to retrieve filterable attributes settings can also return mixed syntax
const response = await client.index(index.uid).getFilterableAttributes();
expect(response).toEqual(newFilterableAttributes);

[Noah-Mack-01]

Hi @Strift,

I'm new to Open Source. Am I good to work on this?
EDIT: I've begun work on this. Will be publishing MR soon. One question: Am I good to change existing test cases which expect a String[] for getFilterableAttributeSettings()? I can add support for a legacy String[] implementation as follows:
[{attributePatterns: ['a','b'], features: {...}},'c'] => ['a','b','c']`

We will obviously be losing attribute metadata in this instance though. LMK!

[Strift]

The API is compatible with both the old and new syntax. So both syntaxes should be allowed to coexist. I'm not sure how close to the JavaScript API we can get with Java, but something similar would be ideal.