feat: updated prover_main.cc and introduce '-n' flag for specifying number …

[whoisgautxm]

Add benchmarking functionality to prover_main.cc

• Introduce '-n' flag for specifying number of proof generation runs
• Implement loop for multiple proof generations
• Calculate and display average and maximum execution times
• Add per-run timing measurements

These changes enable performance analysis across multiple iterations.

[batzor]

Hi @whoisgautxm! Please squash your commits to single commit and your commit message should follow the guideline.

For example, you can say

feat(circom): introduce `-n` flag for specifying number of proof generation runs

In case you're not sure how to do it, you can do git rebase -i HEAD~3 and mark each commits reword, squash, squash :)