[enhancement]: block installation of deprecated adapter npm packages

[mcm1957]

No existing issues.

• There is no existing issue for my request.

Description

Please evaluate if it would be possible (and desired) to prohibit that js-controller (via UI and via cli) installs any adapter release from npm which is marked as deprecated at npm.

Why?

We just had the situation that a broken release could not be unpublished. It is possible to deprectate it.

To prohibit that less experianced users would install this broken release it would be fine if js-controller (and hance cli / admin UI) would no longer install this npm adapter package.

Please note that this ONLY refers to adapter packages. Any dependencies must not be blocked of course

How?

The information that the adapter package is deprecated should be available from npm api and could be checked before startint npm i.

RemarK.
Experienced users which (at least should) know what they are doing can install such a package manually enyway. So I do not see any negative sideeffects. But of course the change should be discussed.

[Apollon77]

We have the blocklist and ignoredVerisons, so the developer can add this to the io-package. Why we need to check this extra?