Ensure @param object type used in function definition (as appropriate)

This is a spin-off from #1820082: Ensure @param array type used in function definition (as appropriate) after thinking about how the sniff/rules for an array type will be simpler than those for an object type. What we want to flag in this issue are the three following types of code examples:

/**
 * Returns the ID of object Foo.
 *
 * @param object $foo
 *   A Foo object.
 *
 * @return string
 *   The ID of this Foo object as a string.
 */
function mymodule_foo_get_id($foo) {

/**
 * Returns the ID of object Foo.
 *
 * @param $foo
 *   A Foo object.
 *
 * @return string
 *   The ID of this Foo object as a string.
 */
function mymodule_foo_get_id(stdClass $foo) {

and/or

/**
 * Returns the ID of object Foo.
 *
 * @param stdClass $foo
 *   A Foo object.
 *
 * @return string
 *   The ID of this Foo object as a string.
 */
function mymodule_foo_get_id(object $foo) {

The purpose of this issue is create a sniff that will identify this type of inconsistency in the future.