[ENHANCEMENT]: Apache-2.0 (or similar) relicensing for `arize-phoenix-client`

[willkill07]

Is your feature request related to a problem? Please describe.

The arize-phoenix-client license is currently Elastic License 2.0 which can be overly restrictive for Open Source project compatibility.

Describe the solution you'd like

In an ideal situation, the arize-phoenix-client could be relicensed to Apache 2.0 or similar license. A relicensing of arize-pheonix-otel has already been done in the past, which solves OTel interfacing, but still does not address interfacing with an Arize Phoenix deployment directly. See #9075 (#9075)

Relicensing the client library would still require anyone using the Arize Phoenix server/service to remain compatible with the license terms of EL 2.0 while still permitting open-source projects to interface with Phoenix without concern of licensing. Since the client cannot be used without the server, the deployment restrictions of arize-phoenix would remain in place while providing users and other open-source projects the flexibility and compatibility of deploying compatible exporters with Phoenix.

[axiomofjoy]

Thanks @willkill07, we're taking a look at the right way to do this on our end.

[mikeldking]

Is this still in progress @axiomofjoy