Reference same node types versions between different components

[pboychev-bcom]

Description

Go through the different TypeScript components and check the Node types versions, update to latest, fix code as needed to support the updated versions.

[pboychev-bcom]

@Indy-rbo, sorry to bother you with this, I remember we discussed the topic in a meeting and since we're looking to start working on the implementation soon, I'd like to make sure we have the same understanding as yours on the matter, could you, please, share again here what the full requirements are /or as full as makes sense :)/, so we don't miss anything? Even if its an example comparison between two components.
Thanks in advance!

[Indy-rbo]

@pboychev-bcom This topic is partly linked to #332. We have local tooling that received errors about some defintions because the node types in some places are of different versions (e.g. vropkg being on ^11.15.7 while vrotsc is on ^14.0.0).

We worked around this by adding in a step in some cases that basically performs npm i -D @types/node@^14.0.0 before our tooling runs but we prefer to not keep this workaround active.

So the requirement would be to have the version of @types/node match the latest (by BTVA supported) node version and have this consistent across the project (like vropkg and vrotsc).

[pboychev-bcom]

Perfect, thanks, @Indy-rbo, exactly what we thought.
On it.