Type conflict between algoliasearch client and its usage in instantSearch

🐛 Bug description

related to: #4911

The InstantSearch client returns upon search with the geo widget the insideBoundingBox field containing a string.

See the following test:

https://github.com/algolia/instantsearch.js/blob/6e6293046de82f90336bc857efa9d0f5fcb8e62b/src/widgets/geo-search/__tests__/geo-search-test.ts#L1717-L1721

Nonetheless the declared type dictates that it should return an array of array of numbers:

see SearchOptions types.

readonly insideBoundingBox?: ReadonlyArray<readonly number[]>;

🔍 Bug reproduction

Steps to reproduce the behavior:

1. Create a custom searchClient for instantSearch
2. Try to adapt insideBoundingBox
3. TypeError

Argument of type 'readonly (readonly number[])[] | undefined' is not assignable to parameter of type 'string'.

💭 Expected behavior

They should be of same type

Environment

• “algoliasearch”: “^4.10.5”,
• “instantsearch.js”: “^4.30.1”,

[Haroenv]

I’d need to check whether the typescript version required in algoliasearch is modern enough to allow template strings, but otherwise, feel free to make a pull request and then it will be fixed @bidoubiwa 😃

[bidoubiwa]

Should be fixed by: https://github.com/algolia/algoliasearch-client-javascript/pull/1310