Fix 1567(1/2): [HelpPage]Api uri not displaying parameter which is a
collection of primitive types and coming from Uri.

     - Add support for primitive/complex collection(and arrays).
     - separate helpers and increase readability.
Fix 1567(2/2): [HelpPage]Api uri not displaying parameter which is a collection of primitive types and coming from Uri.
    This is a separated PR fixing 1567:
        - Add support for generating query string of type Dictionary and KeyValuePair.
        - Replace '.' with '-' in GetFriendlyId. Otherwise, RelativePath with . (like ModelType.Foo or ModelType[0].Foo)
          will break the help page's uri
        - Change the css of help page to make a long path more readable.
Fix 1566: [HelpPage]Change UriParameters display when a parameter with TypeConverter is used

Since we do not know how the string will be parsed with a TypeConverter when generating the
sample query string, just do not display member properties of the type which is associated
with a TypeConverter. Instead, the type itself will be displayed.
Fix 1737: Make TypeHelper.ObjectToDictionary(routeValues) public.
resolve further comments for lower camel case