[enhancement] `evlog/browser` and `evlog/client` are confusing

[MrLightful]

Description

I find two fairly confusing in a sense of documentation and meaning. They are both described in a similar way, yet not quite the same. Also terms for browser and client bear similar meanings.

Proposed Solution

I think evlog/browser would make much more sense when renamed to evlog/api. So it's a drain to custom API. You can drain your client logs to API. Or you can even drain your backend logs to external API.

[MrLightful]

Is there any limitation that prevents using evlog/browser in backend frameworks? I mean, it could also be a use-case. A niche one, but still kinda valid. To drain backend logs to other backend. It wouldn't make sense to use evlog/browser for this, but evlog/api makes total sense.