ci: test latest Node.js

[DanielRuf]

Description

We should test latest / node (alias for same) to fail early (we do not want to change / use 11 when 12 comes out and just maintain the list of LTS versions).

• Closes

Types of changes

• Documentation
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (anything that would change an existing functionality)
• Maintenance (refactor, code cleaning, development tools...)

Checklist

• I have read and follow the CONTRIBUTING.md document.
• The pull request title and template are correctly filled.
• The pull request targets the right branch (develop or develop-v...).
• My commits are correctly titled and contain all relevant information.
• I have updated the documentation accordingly to my changes (if relevant).
• I have added tests to cover my changes (if relevant).

[DanielRuf]

Well, that is bad:
https://blog.github.com/changelog/2018-11-15-force-push-timeline-event/
https://help.github.com/articles/removing-sensitive-data-from-a-repository/

[ncoden]

Well, that is bad

@DanielRuf Is this good to merge or did the PR contained any sensitive data?

[DanielRuf]

It's good to merge now. I've revoked my token (I should have the files in the global ignore file).