feat(javascript): bundle CJS, ESM and UMD

[shortcuts]

🧭 What and Why

🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-232

The PR seems big but most of the changes are generated/from lock files.

Changes included:

• Provide CJS, UMD and ESM output for the JavaScript clients.
• Update playground to test browser

🧪 Test

CI :D

[millotp]

Wow tons of progress ! The flow is quite big, does it alter the creation process of a new client (create file by hand) or is it automatic ?

[eunjae-lee]

Can you split this PR? I see lots of renames, and EchoRequester-related changes.

[shortcuts]

Can you split this PR? I see lots of renames, and EchoRequester-related changes.

I've tried to but all the changes are related to the build. I can do a stacked PR for the echo requester, but it's still required to scope the URL dependency of node/browser builds

[shortcuts]

Wow tons of progress ! The flow is quite big, does it alter the creation process of a new client (create file by hand) or is it automatic ?

The flow should not change, it introduces a new additionalProperties called buildFile, but it can be guessed as it's just the packageName without @algolia/. I believe using a custom generator would remove all of those small parts everywhere

[eunjae-lee]

Can you split this PR? I see lots of renames, and EchoRequester-related changes.

I've tried to but all the changes are related to the build. I can do a stacked PR for the echo requester, but it's still required to scope the URL dependency of node/browser builds

I know it's really troublesome to manage stacked PRs, but it'd be much easier for me to review this PR if there's a PR dedicated to rollup and build process, and another one for the rest.

[shortcuts]

I've kept the weird browser playground for you to test it if you want, but will make it cleaner before merging the PR