Feature c# clients

For C# PdfWebApiClient:
- Refactors/Renames all code to conform C# best practices (checked by FxCop)
- Added/Modified ALL documentation
- Moves ConsoleTestDriver to separate project
- Converts PdfWebApiClient to library/assembly
- Moves Requests into their own directories
- Moves publicly exposed request inner enumerations to their own files in request directories
- Adds LAB color model option to RenderPages
- Adds G3 and G4 compression options to RenderPages
- RenderPages smoothing option is now a bit-flag enumeration so combinational operations can be used
- Versioned C# PdfWebApiClient
- Remove unnecessary bin/obj directories and other misc files
more generally, how important is error handling in a sample client? i think it's ok to throw a null pointer exception if the caller did something silly. after all, this client doesn't even log anything (whereas a production client probably ought to log every request it sends and every response it receives).

i would even remove these Remove calls, even though that makes it harder to reuse the request. i think supporting object reuse is important, but not in this case. a request is fairly lightweight, so reusing it doesn't save much.