npm warn EBADENGINE Unsupported engine for package concentrate@0.2.3

[benfrancis]

STR:

• Run $ npm install from a zigbee-adapter checkout

Expected:

• All dependencies install successfully

Actual:

• Warnings on the console:

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'concentrate@0.2.3',
npm warn EBADENGINE   required: { node: '~0.10.0' },
npm warn EBADENGINE   current: { node: 'v20.19.4', npm: '10.8.2' }
npm warn EBADENGINE }

concentrate@0.2.3 is a dependency of both the unpi and zcl-packet packages but we are currently using our own forked version of those two packages.

$ npm ls concentrate
zigbee-adapter@2.0.0 /home/tola/Code/benfrancis/zigbee-adapter
├─┬ unpi@1.1.1-1 (git+ssh://git@github.com/WebThingsIO/unpi.git#dc2ccb3e6c98c9b8a2bc1cff3b9446bfd9a16dec)
│ └── concentrate@0.2.3
└─┬ zcl-packet@0.2.5-7 (git+ssh://git@github.com/WebThingsIO/zcl-packet.git#d91de72bd2f0f397f9b68b35c43e78e79e54a6ea)
  └── concentrate@0.2.3 deduped

We'll need to either switch to the the latest official versions of those packages if possible, or update our forks if not.

[benfrancis]

Switching from bug to task because not actually causing problems at the moment.

Findings:

• The newest published concentrate on npm is still 0.2.3, and it still declares node ~0.10.0.
• zcl-packet can potentially be moved to upstream 0.3.0 (which no longer depends on concentrate), but this repo currently uses a custom fork and may need code changes.
• unpi still depends on concentrate in latest upstream, so removing it likely requires a fork/patch of unpi.

Note that there are quite a few other dependencies where we use a downstream fork for some version. It would be good to see whether these are still needed.