[tool] Add test_data directory to cognitive complexity check

[camsim99]

camera_android_camerax uses test_data directories for scripts used in evals for skills. Let's include those scripts in the cognitive complexity check. Follow up from #12369 (comment)

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request expands the cognitive_complexity analysis to include Dart files within evals/test_data and specific .agents/skills/ subdirectories, rather than limiting it to the lib/ directory. Feedback suggests optimizing performance by only recursively scanning the specific target directories instead of listing the entire package directory, which can contain large build artifacts.

[gemini-code-assist]

Listing the entire package directory recursively (package.directory.listSync(recursive: true)) is highly inefficient and can cause significant performance bottlenecks in CI/CD pipelines, especially for large packages with many build artifacts (e.g., .dart_tool/, build/, ios/Pods/, node_modules/).

Since we only care about Dart files in lib/, evals/test_data/, and .agents/skills/, we should only recursively list those specific directories if they exist.

    final List<Directory> directoriesToSearch = <Directory>[
      package.libDirectory,
      package.directory.childDirectory('evals').childDirectory('test_data'),
      package.directory.childDirectory('.agents').childDirectory('skills'),
    ];
    final List<String> filesToAnalyze = <String>[];
    for (final Directory dir in directoriesToSearch) {
      if (!dir.existsSync()) {
        continue;
      }
      for (final FileSystemEntity entity in dir.listSync(recursive: true)) {
        if (entity is File && entity.path.endsWith('.dart') && !_isGeneratedDartFile(entity.path)) {
          final String relativePath = path.relative(entity.path, from: package.directory.path);
          final String posixPath = relativePath.replaceAll(r'\', '/');
          final bool isLib = posixPath.startsWith('lib/');
          final bool isRootEvalData = posixPath.startsWith('evals/test_data/');
          final bool isSkillEvalData = 
              posixPath.startsWith('.agents/skills/') && posixPath.contains('/evals/test_data/');
          if (isLib || isRootEvalData || isSkillEvalData) {
            filesToAnalyze.add(posixPath);
          }
        }
      }
    }