ci: node pipelines now setup node version depending on `lockfileVersion`

[derberg]

This is related to very annoying thing about current pipelines, that they are set to Node 14 and in many projects package-lock v2 and even v3 is used, for newer versions of Node. As a result, many times happens that installation of project fail because of inconsistent support between old npm and new package lock structure.

more in https://github.com/asyncapi/.github/pull/187

so what is this PR introducing:

• composite action that can be reused across all repos and we can use it to verify version of package lock, and output proper node version that should be used
• modify pipelines that require Node setup to setup version of the node that given package-lock.json requires

This PR was tested in:

• workflow that uses new composite action https://github.com/derberg/test-experiment/blob/master/.github/workflows/testtest.yml
• composite action taken from this PR, from my fork -> derberg/.github-asyncapi/.github/actions/get-node-version-from-package-lock@d3d8d7452fa3cd5c9970fbb2114e4bafa8a6dabd
• ci run https://github.com/derberg/test-experiment/actions/runs/4734945612/jobs/8404549780

[derberg]

@KhudaDad414 wdyt?

@smoya fyi

@jonaslagoni fyi, this is finally no going to be annoying anymore

[derberg]

/rtm