no-debug also affects log.debug() custom logger

Have you read the Troubleshooting section?

Yes

Plugin version

6.2.0

ESLint version

8.54.0

Node.js version

20.2.0

package manager and version

9.6.6

Operating system

macOS Monterey, 12.7

Bug description

Using a logger in my code, specifically log.debug('')

Steps to reproduce

1. Set up eslint-plugin-testing-library
2. import or write a logger library that uses log.debug (example)
3. type log.debug()
4. Error will fire when linting

Error output/screenshots

error Unexpected debug statement testing-library/no-debugging-utils

ESLint configuration

{
  "env": {
    "shared-node-browser": true,
    "es2022": true
  },
  "ignorePatterns": ["src/app/index.css", "public"],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaVersion": "latest",
    "tsconfigRootDir": ".",
    "project": ["./tsconfig.json", "./tsconfig.node.json"]
  },
  "settings": {
    "react": {
      "version": "detect"
    }
  },
  "plugins": ["testing-library"],
  "testing-library/no-debugging-utils": "error",
}

Rule(s) affected

testing-library/no-debugging-utils

Anything else?

Ideally it would only affect .debug() or when it is using screen or a testing-library helper method.
Alternatively having an option to be able to limit it to screen.debug() would also suffice

Do you want to submit a pull request to fix this bug?

Yes

Start with the testing-library/no-debugging-utils rule and reproduce the reported configuration using a custom logger's log.debug() call. Done means custom logger debug calls are not reported while the rule continues to catch the intended Testing Library debugging usage.