Consider how we might attempt to present vulnerabilities when they occur on multiple branches

This discussion has parallels to the concept of "grouping" that @theoretick has raised in the past during discussions regarding the implementation of Work Item like behavior for vulnerabilities, but essentially the implementation of vulnerability tracking across multiple branches is like to result in a fairly high amount of duplication, especially if a user begins viewing the report with the intent of seeing vulnerabilities across all branches.

If this is desired, it may make sense to begin to attempt to "group" these vulnerability occurrences such that the user can see what vulnerabilities they have at a higher level, and then drill down further into their presence across N branches.

However the troubles with this approach is that is complex to query and present. Theoretically some degree of frontend logic would be capable of handling the group based on the set of records returned in a page with a set of branches, but there may be a variety of pagination and performance related hurdles related to doing this kind of thing.

It's possible that this is out of scope of the original implementation, and something we might simply discuss as a feature improvement in the future once we actually have multiple branch information.