Nicer naming for DB objects.

[colinbull]

I have had a few requests from people I know that are using it (as well as FSharpComposableQuery support (issue #48 and here) , about cleaning up the naming. So things like backticks and [] are minimized, basically so it looks like normal properties. Additionally, this may also include removing _ and case names properly.

On an implementation note, this doesn't look to bad as we can retain the DB name in a type that represents the DB object name.

[pezipink]

I'm all up for making the names nicer, but we need to be careful about how we do it - currently it's just a catch all bucket that will work for everything which is not really ideal, and it can be a little ugly, especially with the schema names prefixed...

The sticky bit is schema names - given we access many data sources and are extensible, in many cases the schema is vital to prevent name collision and to aid clarity - we could possibly move the schema into the provided type hierarchy but that would make everything less convenient to access. We could also try and be clever about the schema names, removing them when there is only the one or there are no collisions, or perhaps allow the implementing interface to define it in some way (for example, Excel and SQLite don't really care about schema).

Another probably obvious thing to note is we will still need to support potential whitespace in object names for sources such as Excel