Concurrency support & lazy generation support for cartesian product generation

[shivasurya]

Is your feature request related to a problem? Please describe.
Similar to CodeQL performance optimization, #116 supports filtering near to the data source and now it warrants optimization using concurrency via multi thread/goroutine and stream result to prevent memory pressure.

When benchmarked against signalapp/Signal-Android, 18,000 methods and 54,000 method invocations - I believe concurrency and streaming support should solve memory pressure issue.

Describe the solution you'd like
Implement goroutine to generate cartesian product

Describe alternatives you've considered

• Using prolog, datalog like native database support
• Apache Calcite for relational algebra evaluation and query optimization

Use case
What will this feature enable for you?
Support larger source code repositories such as signal-android

Additional context
N/A

[shivasurya]

Cartesian product is the last effort. By introducing class based filter backed by storage layer #194 will render cartesian product ineffective solution.