Rework node version tags workflow

[sotojn]

This PR makes the following changes:

• Important: Removed the building and publishing of terascope/node-base-core images
  • This is because there isn't a known use-case for this image
• Updated the following github actions:
  • actions/checkout from v3 to v4
  • docker/login-action from v2 to v3
  • docker/setup-buildx-action from v2 to v3
  • docker/build-push-action from v4 to v6
• Added new workflow that will build and update image tags based off of the latest major node versions
• Added the following labels to the image:
  • node_version
  • kafka_connector_version

Ref to issue terascope/teraslice#3683

[godber]

Rename this PR to match what it does

I had meant for you to build a single image and tag it with multiple tags, somewhat like this:

docker build 22.2.0
docker tag 22.2.0 22.2
docker tag 22.2.0 22
docker push 22.2.0
docker push 22.2
docker push 22

Instead you are doing this, we won't end up with the right versions in these tags ...

docker build 22.2.0 
docker push 22.2.0  <- 22.2.0
docker build 22.2
docker push 22.2     <- 22.2.?
docker build 22        <- 22.4.1
docker push 22  

We always want to have the latest major node version at build time. See if you can rework this.

[godber]

This PR is meant to address the first part of this issue: terascope/teraslice#3683

[busma13]

Looks good.

[godber]

I'm going to go on record here and point out that we were burned by the major number 22 before we even managed to merge this PR. Yesterday everything was fine, today, 22.5.0 came out and broke the kafka install, so we've pinned 22 -> 22.4.1. We will need to remember to address the issue and then come back and unpin it.