feat: use the inferQueryID feature of search-insights

[samyj-alg]

Since v2.15.0, search-insights can keep track of the queryID automatically.
This PR moves the SFRA cartridge to this new built-in method.

Changes

• Upgrade Algolia libraries
• Clean up the former manual mechanism using URL parameters
• Cleans up the existing mechanism to keep track of queryIDs
• Use the new inferQueryID parameter
• Set userHasOptedOut when users have refused the tracking. This is because search-insights.js now systematically uses the browser's local storage to keep track of queryIDs, and since it's not technically necessary data, we need users' consent

[sbellone]

This is not needed, it's done automatically by the browser, I'm removing it.

[sbellone]

Nice cleanup 🙌

[htuzel]

Thank you for the improvement

Need to double check about user tracking

[sbellone]

I'm still tracking the subject.
For visibility:

• I had confirmation that search-insights v2.15.0 systematically uses browser's storage to store queryIDs, without any way to opt-out
• v2.17.2 introduces a way to opt-out
• The frontend libraries are still not using this version, I'm waiting for an update

[sbellone]

Actually, the frontend libraries don't need to be updated, as they use the version that we load manually, so we're good on the 3rd point.

The problem now comes from the 2nd point: opting out is done with the userHasOptedOut flag. But when set to true, everything is disabled: local storage is not used anymore but events are not sent anymore either.
We need and intermediate state: opting-out from using localStorage but still be able to send events.

[sbellone]

I've confirmed with the Events team that it's the expected behaviour and that they won't make further changes for now. Let's merge then!

So userHasOptedOut is now set to true when the user opt-out of tracking, which permits to not use his browser's localStorage in that case (the consequence being that no insights events are sent for those users)