[Draft] Code style

This is a very beginning of defining a code style of the lib

1. Use using instead of typedef - using is more readable
2. Class can have super alias in its' score only to its' superclass. Otherwise give it a different name
3. Curly braces after if, for and while must be put on the same line not on the next one - same code less lines
4. All classes/structs are named with lowercase with underscore just like std's ones - one of sqlite_orm's goals is to look like it is a part of stdlib: storage_t, table_type, statement_binder
5. private variables are named with camelcase: needQuotes, compositeKeyColumnNames
6. public functions are named just like classes: begin, make_table, bind