File inclusion - check for constant defined in the current file

## What problem would the enhancement address for VIP?

The frequency with which "Warning: File inclusion using custom constant (`PREFIX_PATH`). Probably needs manual inspection (WordPressVIPMinimum.Files.IncludingFile.UsingCustomConstant)." shows up just below a line that matches the pattern is high.

Perhaps we can reduce this noise.

## Describe the solution you'd like

See if we can improve the sniff, to see if the constant has been defined in the current file, and if so, skip the violation.

## What code should be reported as a violation?

```php
require PREFIX_PATH_UNDEFINED_IN_THIS_FILE . '/...';
```

## What code should *not* be reported as a violation?

```php
define( 'PREFIX_PATH_DEFINED_IN_THIS_FILE', '...' );
...other code...
require PREFIX_PATH_DEFINED_IN_THIS_FILE . '/...';
```

Inizia individuando lo sniff che emette WordPressVIPMinimum.Files.IncludingFile.UsingCustomConstant e verifica come rileva le costanti nelle espressioni di inclusione dei file. Aggiungi una copertura per l’esempio della costante non definita e per la costante definita in precedenza nello stesso file; il lavoro è completato quando viene segnalato solo il caso della costante non definita.

Scritto dal modello di indicizzazione a partire dal testo della issue.