feat: basic tests and doc changes for no-scan mode

[joydeep049]

Related Discussion : #5136

cc @terriko @anthonyharrison @mastersans

[mastersans]

seems like this particular test is failing.

[joydeep049]

Yes, Initially I tried cve-bin-tool <directory> --no-scan but that failed
Then I changed the entry point to cve_bin_tool/cli.py but that seems to fail too

Surprising how --no-scan shows up in python3 cve_bin_tool/cli.py --help but not in the above

[joydeep049]

Re-running the tests with an empty commit because:

[terriko]

FYI: still failing:

 =========================== short test summary info ===========================
FAILED test/test_no_scan.py::test_normal_scan - TypeError: argument of type 'NoneType' is not iterable
===== 1 failed, 2275 passed, 48 skipped, 8 warnings in 3420.69s (0:57:00) =====

There's also a pyupgrade linter fail so you should probably run that and see what got deprecated.

[stvml]

Looks like this might be the underlying issue that caused the failure:

test/test_no_scan.py::test_normal_scan
  C:\hostedtoolcache\windows\Python\3.12.10\x64\Lib\site-packages\_pytest\threadexception.py:58: PytestUnhandledThreadExceptionWarning: Exception in thread Thread-5 (_readerthread)
  
  Traceback (most recent call last):
    File "C:\hostedtoolcache\windows\Python\3.12.10\x64\Lib\threading.py", line 1075, in _bootstrap_inner
      self.run()
    File "C:\hostedtoolcache\windows\Python\3.12.10\x64\Lib\threading.py", line 1012, in run
      self._target(*self._args, **self._kwargs)
    File "C:\hostedtoolcache\windows\Python\3.12.10\x64\Lib\subprocess.py", line 1599, in _readerthread
      buffer.append(fh.read())
                    ^^^^^^^^^
    File "C:\hostedtoolcache\windows\Python\3.12.10\x64\Lib\encodings\cp1252.py", line 23, in decode
      return codecs.charmap_decode(input,self.errors,decoding_table)[0]
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  UnicodeDecodeError: 'charmap' codec can't decode byte 0x90 in position 21620: character maps to <undefined>

Possibly a text encoding problem on Windows?