[Feature request] Allow to configure an array of purls to scan in the configuration file.

[mtrx1337]

First of all - we love your project. Thank you for building this amazing tool.

Right now only github repositories and organizations can be scanned. We have a long list of purls that we would like to scan. This means we need to build a custom solution to scan them with multiple fosstars instances (passing the purl as a command line argument), instead of writing a configuration file.

[sourabhsparkala]

@mtrx1337 thank you for creating this request, could you maybe provide more information on your usecase?, How do you want to pass the arguments if not a config file? Does it make sense to get the purl list from a config file? WOuld that serve your purpose?

[mtrx1337]

I have a list of ~700 purls in a CSV. You are right, it should not be expected to put these in the configuration file. Maybe it would be a better solution to allow loading purls / github urls from a (CSV|JSON|YAML) file?

Before I already generated a configuration file from the default template with ~1200 organization/name pairs. This could've been easier with just allowing to load a CSV of github URLs.