Migrate vul chain finder to data processing platform

[ashkboos]

In this PR we migrate the proof of concept implementation of VulChainFinder in the old repository to the data-processing platform.

[mir-am]

BTW, you can also use JOOQ's methods to get vulnerable callables given a module id instead of using a raw SQL query.

[mir-am]

I have talked to Sebastian (@proksch) and we have decided that I can work on this feature branch, address the above comments, and deploy it on monster for the vulnerability paper(s).
That said, we are not going to merge it until the final code review and your approval.
I would like to ask you, Mehdi (@ashkboos ), whether you are also okay with this, i.e, me working on this feature branch.

[ashkboos]

I have talked to Sebastian (@proksch) and we have decided that I can work on this feature branch, address the above comments, and deploy it on monster for the vulnerability paper(s). That said, we are not going to merge it until the final code review and your approval. I would like to ask you, Mehdi (@ashkboos ), whether you are also okay with this, i.e, me working on this feature branch.

Yes sure, no need to even ask Amir. And sorry for not addressing the comments so far, I was waiting for the code review session that we planned to do on this PR to look at it together in person but unfortunately, it got postponed multiple times.

[proksch]

I have updated (and rebased) the branch to include the latest changes that were necessary to adopt changes from core. The build should work again and use all up-to-date classes/plugins.

While updating, I also checked the implementation a bit... maybe we should make this plugin subject of a pair programming Monday to clarify some things about the loader platform and to talk about recurring issues that I found in several places in the code.

I am also not particularly sure about the introduction of the new Error class for exception handling... I would like to discuss this with you in person before we release this plugin.