The `static` keyword is generally tokenized as `T_STATIC`. However, in PHPCS 3.x, there was one exception - when `static` was used in an `instanceof static` expression, the `static` keyword was tokenized as `T_STRING`.

As of PHPCS 4.0, this exception has been removed and `static` in `instanceof static` will now also be tokenized as `T_STATIC`.

This commit removes the code handling the PHPCS 3.x exception.

…ners

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

…nthesis owners

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

…wners

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

As of PHPCS 4.0, `T_USE` (for closures), `T_ISSET`, `T_UNSET`, `T_EMPTY`, `T_EVAL`, `T_EXIT` are parenthesis owners, so we don't need to token walk to search for the parenthesis opener/closer anymore, we can just access the token stream array indexes directly.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to skip over a `T_NS_SEPARATOR` token for a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaces names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaces names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaces names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This means we can remove some code which is no longer needed as, for instance, a namespace relative name `namespace\something` will no longer use the `T_NAMESPACE` token.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to skip over a `T_NS_SEPARATOR` token for a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check if a `T_STRING` token is a namespaced name, as if it were, it would be tokenized differently.

As of PHPCS 4.0, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check for a `T_NS_SEPARATOR` token for a fully qualified call to exit/die, as that will be tokenized as part of the `T_EXIT` token as of PHPCS 4.0.

As of PHPCS, namespaced names use the tokenization as per PHP 8.0. This also means that we no longer need to check for `T_NS_SEPARATOR` or `T_NAMESPACE` tokens when examining names.

The `Collections::namespacedNameTokens()` token array contains the PHPCS cross-version compatible tokens, while the `Collections::nameTokens()` token array contains only the tokens we need to take into account for PHPCS 4.x.