tokenizer is not case-sensitive for keyword determination

Consider the following valid SQL statement:
`UPDATE machine_boards21
SET type = 'hybrid', model = 'LX21'
WHERE id = 'machine1';`

tokenizing produces the following output:
`Word(Word { value: "UPDATE", quote_style: None, keyword: UPDATE }), Whitespace(Space), Word(Word { value: "machine_boards21", quote_style: None, keyword: NoKeyword }), Whitespace(Newline), Word(Word { value: "SET", quote_style: None, keyword: SET }), Whitespace(Space), Word(Word { value: "type", quote_style: None, keyword: TYPE }), Whitespace(Space), Eq, Whitespace(Space), SingleQuotedString("hybrid"), Comma, Whitespace(Space), Word(Word { value: "model", quote_style: None, keyword: NoKeyword }), Whitespace(Space), Eq, Whitespace(Space), SingleQuotedString("LG"), Whitespace(Newline), Word(Word { value: "WHERE", quote_style: None, keyword: WHERE }), Whitespace(Space), Word(Word { value: "id", quote_style: None, keyword: NoKeyword }), Whitespace(Space), Eq, Whitespace(Space), SingleQuotedString("machine1"), SemiColon]`

notice how the 'type' token was interpreted: `Word(Word { value: "type", quote_style: None, keyword: TYPE })`

keyword TYPE... This causes an issue in `parse_assignments()` when `parse_identifiers_non_keywords()` is called

The error ultimately thrown by `calling parse_statement()` on this statement is as follows:
`ParserError("Expected =, found: type")`

Reproduce la sentencia SQL del issue e inspecciona parse_assignments(), especialmente su llamada a parse_identifiers_non_keywords(). Sigue cómo el tokenizer asigna la palabra clave TYPE al token type sin comillas; se considera terminado cuando la sentencia se analiza correctamente sin tratar ese identificador como una palabra clave.

Escrito por el modelo de indexación a partir del texto del issue.