The returned Type is never a wildcard due to the changes made to getSupertype
by commit b1fb9ca.

getRawType(TypeToken.getType()) is the same as calling TypeToken.getRawType().

It is possible to use wildcards as part of the type argument, e.g.:
`new TypeToken<List<? extends CharSequence>>() {}`

Previously subclasses of subclasses (...) of TypeToken were allowed which
can behave incorrectly when retrieving the type argument, e.g.:

  class SubTypeToken<T> extends TypeToken<Integer> {}
  new SubTypeToken<String>() {}.getType()

This returned `String` despite the class extending TypeToken<Integer>.

Due to type erasure the runtime type argument for a type variable is not
available. Therefore there is no point in capturing a type variable and it
might even give a false sense of type-safety.

Rename the method parameter to match the documentation of the method and
to be similar to getSupertype(...).

…tic accessors

As mentioned in review comments, there are cases during serialization where
usage of the type variable is not so problematic (but still not ideal).