Visually identify rules that use fs.*

Enabling any of these rules causes dramatic slow down.

For context, running eslint against our project with 3,000+ files takes ~3 minutes with any of these rules enabled, and just another 20 seconds otherwise.

A simple indication in documentation that these rules cause the slowdown would be sufficient.

```json
{
"import/no-relative-parent-imports": 0,
"import/no-relative-packages": 0,
"import/no-unresolved": 0,
"import/no-extraneous-dependencies": 0,
"import/no-unused-modules": 0,
"import/no-restricted-paths": 0,
"import/no-duplicates": 0,
"import/no-useless-path-segments": 0,
"import/no-cycle": 0,
"import/no-internal-modules": 0,
"import/extensions": 0,
"import/no-self-import": 0
}
```

I identified these rules by checking which rules include `eslint-module-utils/resolve`.

Start by locating the documentation entries for the listed rules and check how rule performance or filesystem resolution is currently described. Mark the rules that use eslint-module-utils/resolve as potentially slow, and consider the work done when users can identify those rules from the documentation.

Written by the indexing model from the issue text.