ci(travis): leverage commitlint travis helper

[ChristianMurphy]

removes need for custom shell script to check commit messages.
moves greenkeeper-lockfile package into dev dependencies so updates can be tracked.

---

Contributor License Agreement adherence:

• This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

[ChristianMurphy]

CI error is originating from https://github.com/marionebl/commitlint/pull/157
Upstream resolution coming soon.

[marionebl]

Chiming in here - the travis helper isn't quite ready for prime time yet. I am working out the kinks, tracking progress here: https://github.com/marionebl/commitlint/issues/99, testing reports welcome!

[ChristianMurphy]

the travis helper now is a officially recommended method https://github.com/marionebl/commitlint/pull/215
Updating this PR to get it merge-able.

[ChristianMurphy]

AppVeyor failing on unrelated issue

[INFO] --- exec-maven-plugin:1.3.2:exec (npm install (initialize)) @ uportal-app-framework ---
npm ERR! path C:\projects\uportal-app-framework\node_modules\fsevents\node_modules
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall scandir
npm ERR! Error: EPERM: operation not permitted, scandir 'C:\projects\uportal-app-framework\node_modules\fsevents\node_modules'
npm ERR!  { Error: EPERM: operation not permitted, scandir 'C:\projects\uportal-app-framework\node_modules\fsevents\node_modules'
npm ERR!   stack: 'Error: EPERM: operation not permitted, scandir \'C:\\projects\\uportal-app-framework\\node_modules\\fsevents\\node_modules\'',
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'scandir',
npm ERR!   path: 'C:\\projects\\uportal-app-framework\\node_modules\\fsevents\\node_modules' }
npm ERR! 
npm ERR! Please try running this command again as root/Administrator.

[ChristianMurphy]

@uPortal-Project/uportal-app-framework-committers I'm invoking lazy consensus on this task.
Barring any objections, I plan on merging this later today.

[apetro]

I'd prefer that lazy consensus invocations have a footprint on uportal-dev@.

[ChristianMurphy]

I'd prefer that lazy consensus invocations have a footprint on uportal-dev@

😒
Lazy consensus is a way of clearing blockers.
I'm not fully onboard with encouraging it.
Ideally people should be reviewing, and leaving explicit 👍 or 👎.