add error information about sqlite keywords usage

[ghost]

No description provided.

[mention-bot]

By analyzing the blame information on this pull request, we identified @sibeliusseraphini, @RoyMontoya and @whoshuu to be potential reviewers

[bpappin]

Just a couple of suggestions:

1. It might be easier to maintain as an array of keywords instead of a list. Since it only runs when the generator runs, and is immutable, the collection is a bit overkill.
2. in createTableSQL(), you should output the name of the keyword in the error so the developer can easily figure out which column has a bad name.

[coveralls]

Coverage increased (+3.0%) to 70.461% when pulling a0dc1cc on geracervantes:master into 2358dae on satyan:master.

[sibelius]

this should be static

[sibelius]

@geracervantes or @JonatanSalas, could someone change from Set to an Array

array of keywords instead of a list

and also address this:

in createTableSQL(), you should output the name of the keyword in the error so the developer can easily figure out which column has a bad name.

and use static method instead of creating a KeyWords object

[ghost]

working on it