Get correct node version to make Kibana work on ppc64le, otherwise bu…

[vaibhavsood]

Have run npm run build and npm run test on ppc64le, everything passes
Only change needed is to use correct node version

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you included unit tests that cover the changes?
• If submitting code, have you tested and built your code locally prior to submission with npm test && npm run build?
• If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.

…ilds and all test suites pass on ppc64le

[elasticsearch-release]

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then say 'jenkins, test it'.

[epixa]

Thanks for the PR, but we're not prepared to support a new architecture for Kibana builds. Any new architecture takes a considerable amount of time to set up the necessary development and testing infrastructure required to ensure stable releases, and then it adds QA time and effort to every release going forward, so we can't take adding new architectures lightly.

[karmi]

Hi @vaibhavsood, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?