Normalize package.json files, to prepare publication on NPM

[Kocal]

Q	A
Bug fix?	no
New feature?	no
Issues	Fix #...
License	MIT

This is a first iteration for #2575: rework our package.json files in order to make them more "friendly" and work on npm.

Next steps:

1. Add some verifications, to ensure PHP and JS versions of a same package are identical (and so 100% compatible)
2. See how we can deploy JS packages when creating a new UX releases. I'm thinking about a full automated process using the CI with a workflow listening on tag creation, which will be responsible to upgrade the version from package.json files, commit, push, and publish to npm)
3. Check if we need to manually create the packages on npm before trying to publishing them

[smnandre]

Question: should this be the monorepo or the split one ?

( https://github.com/symfony/ux-autocomplete [...] ) ?

[Kocal]

Let's use splited repositories

[skmedix]

I wouldn't mind using monorepo here, as it is a go-to place for proposing contributions etc

[smnandre]

Problem is, JsDeliver, Packagist, etc;... do not work well with monorepo... so it depends on "how" this package.json attribute is used (I have no idea so I will trust you guys on this)

[skmedix]

Fair enough then 👍