chore: switch to 'npm workspaces'

[trentm]

Let's try npm workspaces for handling multiple packages. The primary win is developing local changes to the helpers package and having the others automatically linked.

Note that npm workspaces requires npm@7 or later, which typically means node@16 or later. For earler Node.js versions there are utils/run-* scripts to support install/test/lint.

[david-luna]

I've tested make all to see what's the result:

• package-lock.json files are generated on each package. Maybe we want to ignore them
• packages are not linked between them, instead the have a downloaded version from the registry

The second point may difficult to do changes in more than one package at the same time (I think they can manually nom link). We may want to highlight that in the contributing guide. This is a nitpick

[trentm]

I've tested make all to see what's the result:

* `package-lock.json` files are generated on each package. Maybe we want to ignore them

What version of node and npm were you using with this?
With node <16 and npm <7 this is the expected behaviour.

With node 18 I get:

% npm --workspaces install
...

% npm ls
@elastic/ecs-logging-nodejs@ /Users/trentm/el/ecs-logging-nodejs4
├─┬ @elastic/[email protected] -> ./packages/ecs-helpers
│ ├── @hapi/[email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └── [email protected]
├─┬ @elastic/[email protected] -> ./packages/ecs-morgan-format
│ ├── @elastic/[email protected] deduped -> ./packages/ecs-helpers
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected] deduped
│ └── [email protected] deduped
├─┬ @elastic/[email protected] -> ./packages/ecs-pino-format
│ ├── @elastic/[email protected] deduped -> ./packages/ecs-helpers
│ ├── @types/[email protected]
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected] deduped
│ ├── [email protected] deduped
│ └── [email protected] deduped
└─┬ @elastic/[email protected] -> ./packages/ecs-winston-format
  ├── @elastic/[email protected] deduped -> ./packages/ecs-helpers
  ├── [email protected] deduped
  ├── [email protected] deduped
  ├── [email protected]
  ├── [email protected] deduped
  ├── [email protected] deduped
  ├── [email protected] deduped
  ├── [email protected] deduped
  ├── [email protected] deduped
  └── [email protected]

[david-luna]

With node <16 and npm <7 this is the expected behaviour.

Then it's okay. It will be obvious if someone with node < 16 and npm < 7 creates a PR and accidentally includes those files.