linter: check resolved config if `ModuleRecord`s are needed

Currently, the linter runtime accepts an option cross_module and enables the resolver for the import plugin at a global level:

https://github.com/oxc-project/oxc/blob/c79696618342688b8849afd649d4a3f42f008b63/crates/oxc_linter/src/service/runtime.rs#L290-L292

https://github.com/oxc-project/oxc/blob/c79696618342688b8849afd649d4a3f42f008b63/apps/oxlint/src/lint.rs#L281-L282

There could be configs nested configs / overrides, which will only require the import plugin for specific files / directory.

Example:

{
  "plugins": ["oxc", "typescript"],
  "overrides": [
    {
     "files": ["new_codebase/**/*.ts"],
     "plugins": ["import"]
    }
  ]
}

Or for a nested example:

// /root/.oxlintrc.json
{
  "plugins": ["oxc", "typescript"]
}

// /root/subdirectory/.oxlintrc.json
{
  "plugins": ["oxc", "typescript", "import"],
}

Depending on the file, the Runtime could skip the dependencies of the file:
https://github.com/oxc-project/oxc/blob/c79696618342688b8849afd649d4a3f42f008b63/crates/oxc_linter/src/service/runtime.rs#L378-L382

Start with the linked sections of crates/oxc_linter/src/service/runtime.rs and apps/oxlint/src/lint.rs. Trace how resolved configurations, overrides, and nested configs are represented before examining the dependency-skipping path in runtime.rs. Done means dependency handling reflects whether the current file's resolved config requires ModuleRecords, including per-file plugin activation.