fix pragmas, indentation and expose plutus-benchmark-common

[perturbing]

I often like to depend on this lib outside of plutus to experiements and test how costly things are. Like I did here (note that this depends on a custom fork already exposing this lib).

Can we permanently expose this lib in plutus?

[github-actions]

PR Preview Action v1.6.2
🚀 View preview at https://IntersectMBO.github.io/plutus/pr-preview/pr-7292/
Built to branch gh-pages at 2025-08-28 21:17 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[effectfully]

I have no issue with plutus-benchmark being exposed publicly as long as folks understand that we may break backwards compatibility at will.

[effectfully]

It's enabled globally in plutus-benchmark.cabal, so it shouldn't be needed here.

[kwxm]

@perturbing Did you have some reason for adding that, like you needed it to use a copy of the code outside our repository? I've removed this and another one that don't seem to be needed.

[kwxm]

There's a question about whether this would mean that we'd have to include plutus-benchmark in the Plutus release process and release it to CHaP. An alternative would be to move the relevant code to plutus-ledger-api (which it depends on anyway, although maybe that's not really the right place for it).

@zliu41: what do you think?

[zliu41]

Can we permanently expose this lib in plutus?

If adding visibility: public is all you need, that's totally fine.