Codemodder should not report scanned files if no codemods ran

[clavedeluna]

This is new behavior that I think we should tweak. Take a look at the output of this command
codemodder tests/samples/ --output here.txt --codemod-include=bad

[startup]
codemodder: python/0.84.1.dev25+g7f5d2ca.d20240313
command: codemodder tests/samples/ --output here.txt --codemod-include=bad
Requested codemod to include'bad' does not exist.

[setup]
running:
including paths:
  - **.py
  - **/*.py
excluding paths:
  - test/**
  - tests/**
  - **/__test__/**
  - **/__tests__/**
  - conftest.py
  - build/**
  - dist/**
  - venv/**
  - .venv/**
  - .tox/**
  - .nox/**
  - .eggs/**
  - .git/**
  - .mypy_cache/**
  - .pytest_cache/**
  - .hypothesis/**
  - .coverage*

[scanning]
no codemods to run

[report]
scanned: 63 files
failed: 0 files (0 unique)
changed: 0 files (0 unique)
report file: here.txt
total elapsed: 222 ms
  semgrep:     0 ms
  parse:       0 ms
  transform:   0 ms
  write:       0 ms

I don't think we should be logging scanned: 63 files since we also log "no codemods to run". instead it should bescanned: 0 files for consistency.