As a non-controller with empty state, `NftDetectionController` should not inherit from `BaseController`

## Requirements

- Should not inherit from `BaseControllerV1` or `BaseController`.
- Should not use the `Controller` suffix in its name.
- Types for `ControllerState`, `ControllerGetStateAction`, `ControllerStateChangeEvent` should not be defined or exported.
- Should accept `messenger` as a constructor option.
- `messenger` should be defined with allowlists that enable the class to make all communications with other controller classes that were previously supported.
- ~Should not accept any class method callbacks as constructor options. Messenger actions/events should be used to communicate instead.~
- ~In some cases, methods that implement API interactions should be extracted into a dedicated `service` class.~

No file or test is named in the issue. Locate NftDetectionController, BaseControllerV1, BaseController, and the referenced controller state types, then trace the existing controller communications before changing the class boundary. Done means the class meets each listed inheritance, naming, export, constructor, and messenger-allowlist requirement.

Written by the indexing model from the issue text.