feat: No-Scan SOC for binary checker pipeline

[joydeep049]

Separation of Concerns of the checker pipeline for No Scan Mode.

Currently if we use --no-scan flag in the CLI the language parser pipeline is skipped and the binary checker scan is run without any interaction from the database. I have added a few extra logs in order to visualize everything better, which I will remove in further iterations.

@terriko @anthonyharrison @mastersans

[terriko]

As I said, let's switch most of the logs to be debug instesad of info (just so we don't have a bunch of surprise noise if I manage to cut a release next week) but otherwise I think we're good. It would be nice to have a really simple test along the lines of "does the --no-scan command line option exist and not fail if you use it" to go with this, but it can be a separate PR (maybe a nice easy one for next week while you're working on the language parser stuff). Docs can wait until we're a bit further along into having it work as expected.

[terriko]

Oh! Also, I'll try to get you set up in a group so your CI will run automatically without having to wait for me, so if you get an invite to some github group that starts with cve-bin-tool- that's what that's going to be about. I just need to go figure out what the right group name is and open a ticket with our ops folk.

[anthonyharrison]

Can we update the README with the new option?

[terriko]

I'm going to get this merged as-is, but I'll set up an issue reminding us that we want a test and a preliminary docs entry (likely explaining what works and what doesn't, such as the fact that it won't operate without cve data yet)

Moving docs to separate PR