Use generated types from AVDL

[nathanmsmith]

Take advantage of node-avdl-compiler 1.4.1 to generate our types.

Some notes:

• Since this changes some variable names, this would be a breaking change. I have "Version 2" project to track other changes I think would make sense to go in a 2.0. It seems like the two ways to upgrade version in go is to create a version git tag, separate v2 branch, or v2 subdirectory in the repo. Would love to hear which approach y'all like best, I'm leaning towards tagging.
• I added a Makefile to generate the types from this repo. The Makefile utilizes the tooling inside the client repo.
• The README and examples should be updated.

[nathanmsmith]

I moved govet and golint to be run by golanglint-ci instead of separately. Main reason for this is that it allows us to specify the same ignore config for all linters, but I believe it'd would also be faster?

[nathanmsmith]

If you have a makefile in your go project, travis won't auto detect and install dependencies; it expects you to have a task for that.

[mmaxim]

Why not just vendor the types in, why do we need to generate them in here?