Discuss the impact of additional vulnerability entry points, as well as the possible impact of partial scanning

The following discussion from !12117 (merged) should be addressed.

@hacks4oats has pointed out that a growing contingent of customers desire partial scanning mechanics to improve security scan efficiency. This may prove problematic should we be reliant on full vulnerability scans to determine changes in vulnerability state and presence when changes to the git tree occur. (Such as merges, rebases, dropping of branches or commits, etc)

Additionally, @minac raised that there are additional vulnerability entry points other than the standard commit and scan lifecycle (such as starboard and manual vulnerabilities). We should consider how these vulnerabilities are tracked across multiple branches and impact the proposed solution.