Move away from nodejs4 in an Openstack context

First I voluntarely ignored 'x' projects. These changes are only against
openstack projects.

We recently experienced inconsistencies between yarn and the nodejs
version in use in some environments [1]. This problem have been fixed [2]
by Adding the nodejs10-publish-to-npm project template [3] and by using
it on the project that failed [4].

However today we started to experience the same issue again [5] on another
project (eslint-config-openstack).

These changes move this project under nodejs10.

Also these changes propose to move to nodejs10 all the projects under the
openstack umbrella.

[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021002.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/021207.html
[3] https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/781825/
[4] https://review.opendev.org/c/openstack/project-config/+/781826/
[5] http://lists.openstack.org/pipermail/release-job-failures/2021-April/001525.html

Change-Id: I208646b1701fde8e743a645a77ab73dcdc0a55a1

zuul.d/projects.yaml

@@ -2476,7 +2476,7 @@
 - project:
     name: openstack/eslint-config-openstack
     templates:
-      - nodejs4-publish-to-npm
+      - nodejs10-publish-to-npm
       - official-openstack-repo-jobs
 
 - project:
@@ -2786,13 +2786,13 @@
 - project:
     name: openstack/js-openstack-lib
     templates:
-      - nodejs4-publish-to-npm
+      - nodejs10-publish-to-npm
       - official-openstack-repo-jobs
 
 - project:
     name: openstack/karma-subunit-reporter
     templates:
-      - nodejs4-publish-to-npm
+      - nodejs10-publish-to-npm
       - official-openstack-repo-jobs
 
 - project:
@@ -3139,7 +3139,7 @@
 - project:
     name: openstack/monasca-kibana-plugin
     templates:
-      - nodejs4-publish-to-npm
+      - nodejs10-publish-to-npm
       - official-openstack-repo-jobs
 
 - project: