clp-bench: Refactor and Add New Results

[anlowee]

This PR does a major refactoring. The main change is that we lock the clp-bench executor's code logic, for each target tool, the user shall provide corresponding scripts that to execute tasks of benchmarking.

Benefits:

• No need to modify the clp-bench package's code everytime we add a new target tool to benchmark against.
• The scripts of each target tool are stored in a asset folder, which is clear and easy to manage.

[kirkrodrigues]

Sorry, won't be able to review this until tonight.

[kirkrodrigues]

Sorry, was sick over the weekend so didn't get a chance to look at this. Will review at least the docs today.

[anlowee]

Sorry, was sick over the weekend so didn't get a chance to look at this. Will review at least the docs today.

Take care! It becomes very vold suddenly these days.

[kirkrodrigues]

Some feedback on the docs. I would also like to clean up the directory structure, but I guess that may take you some time, so we can defer it to the next PR.

[kirkrodrigues]

Some additional comments besides those inline:

• For all Markdown link references (i.e., the b in [a][b]):
  • can we avoid using spaces?
  • can we keep them short (that's the goal of using link references)?

Thanks for making the changes requested so far. To give you some context, my goal is that we get this PR to a state where the docs and usage are clear. Then we can defer any additional refactoring to future PRs.

[kirkrodrigues]

Sorry, need a little more time to finish reviewing this.

[kirkrodrigues]

Is the first flowchart in the methodology being displayed as you expect?

[anlowee]

Is the first flowchart in the methodology being displayed as you expect?

Apparently no lol, so weird. It should look like this:

Don't know why it gets rendered so weirdly on github

[anlowee]

Is the first flowchart in the methodology being displayed as you expect?

Fixed this in the latest commit