Add Bencher to track Benchmarks Performance Regression

[Robertorosmaninho]

Fixes #3517
Follow up of #3603

This PR Introduces Bencher.dev to track performance regressions on our benchmarks.
The Benchmarks already run in the Test-PR Workflow as "Performance Tests" CI. This PR introduces a third-party program that will collect the JSON results of these executions and display them in a graphical online tool.

It will also set a threshold for the time/space that each test, and if an execution passes this limit, the tool will post a comment on the PR warning the developer which tests the regression was observed. The CI will also fail, which won't prevent the PR from being merged.

[Robertorosmaninho]

Add -v to kompile

[Robertorosmaninho]

@radumereuta I've addressed your comments, and I'm now removing the kompiled directory after each iteration. Although, I think the appropriate solution would be a new frontend flag like --no-cache or --do-not-use-cache.

The flag --profile-rule-parsing indeed does this, but it does more than we want as well, so it's a workaround as much as deleting the directory. I choose the last option as it's more strict for our purpose here.

[radumereuta]

lgtm
Deleting the directory is the safest option. It's too easy to mess something up in the code and get erroneous results.
I would like it if someone else also had a look at the PR.
Great work, though.

[F-WRunTime]

I can't comment on the lower level Makefiles but the changes to the workflow look reasonable

[dwightguth]

Looks good, but where is the link to the results?

[Robertorosmaninho]

Looks good, but where is the link to the results?

The link for each result is generated after every execution of bencher run on the Performance Tests CI under the Profiling Performance Tests step as:

View results:
- AVM-SEMANTICS (Elapsed Real time (wall clock) in Seconds): https://bencher.dev/console/projects/k-framework/perf?metric_kind=build-time&branches=7fba2f4e-5e87-4782-92a7-9dfc4c8aaa1d&testbeds=d9eea46c-dd6c-4d0e-a830-30581a4e4446&benchmarks=3744f607-9385-4366-a682-5128ce2df25f
- AVM-SEMANTICS (Maximum Resident Set Size in KB): https://bencher.dev/console/projects/k-framework/perf?metric_kind=max-resident-set-size&branches=7fba2f4e-5e87-4782-92a7-9dfc4c8aaa1d&testbeds=d9eea46c-dd6c-4d0e-a830-30581a4e4446&benchmarks=3744f607-9385-4366-a682-5128ce2df25f

.
But for a general purpose, we can define this as the Main Benchmark Page.