enforce-node-protocol-usage conflicts with no-unresolved

I have enabled the [`import/enforce-node-protocol-usage`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/enforce-node-protocol-usage.md) rule as mentioned in [this comment](https://github.com/import-js/eslint-plugin-import/issues/3193#issuecomment-3005628582). After running ESLint, I am encountering the following error of [`import/no-unresolved`](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-unresolved.md):

```text
error Unable to resolve path to module 'node:fs' import/no-unresolved
```

Is this a bug, or is there a configuration step I need to follow to resolve node protocol module imports when using this rule?

Any guidance on how to fix this would be appreciated.

Start with the documented import/enforce-node-protocol-usage and import/no-unresolved rules linked in the issue, then reproduce the reported node:fs error with both rules enabled. Done means node protocol imports are handled without an incorrect no-unresolved error, or the required configuration is documented.

Written by the indexing model from the issue text.