Refactor easyjson with encoding/json

[Ja7ad]

Description
We propose removing easyjson and refactoring the SDK to use the built-in encoding/json package. Although easyjson provides performance benefits, it has limitations when dealing with dynamic types, such as interface{} in search results. This was highlighted in #436, where large numeric values encountered precision issues. Switching to encoding/json would improve flexibility, maintainability, and error handling.

Basic example

// Replace easyjson.Marshal with json.Marshal
json.Marshal(data)

[Ja7ad]

Hits field with type *[]map[string]json.RawMessage and unmarshaled value fixed without write custom marshaler.

[Ja7ad]

easyjson make complex client for unmarshaling.

[hegdeshashank73]

Is this issue still open @Ja7ad . Wanted to pick it up

[Ja7ad]

Is this issue still open @Ja7ad . Wanted to pick it up

Yes I'm working on this issue #582

[curquiza]

@hegdeshashank73 thank you for your interest. The issue is already picked up, however, you are always welcome to provide review on the PR #582 😊