Review how docblock class imports are handled

I noticed that in the docblocks we are unsing FQCN when adding types to the parameters. We are also importing those at the top of the file.

In most of the editors, the editor is smart enough that it will know to what class/interface we are referring to.

So we should consider maybe shortening the FQCNs in the docblocks?

Example:

<?php
...

namespace WordPressCS\WordPress\Helpers;

use PHP_CodeSniffer\Files\File;
...
// Later in the class/trait/interface:
	/**
	 * ...
	 * @param \PHP_CodeSniffer\Files\File $phpcsFile The file being scanned.

Could be written as:

<?php
...

namespace WordPressCS\WordPress\Helpers;

use PHP_CodeSniffer\Files\File;
...
// Later in the class/trait/interface:
	/**
	 * ...
	 * @param File $phpcsFile The file being scanned.

As the File is imported at the top of the file.

Thoughts?

Review the repository's PHP docblocks and their top-level imports, using the issue's PHP_CodeSniffer\Files\File example as the starting point. The work is done when the project has a decided convention for imported docblock types and the affected usages follow it consistently.