Plutus Quantitative Timeliness Agreements, aka QTAs

[nfrisby]

@njd42 suggested these a while ago, and there was some planning around them, but for various reasons (I think personnel churn), the work disappeared.

The basic idea (feel free to edit this, Neil) is that the different components/teams need to specify their expected performance profiles, and add some benchmarks/tests to catch performance regressions/violations.

For now, I'm just opening this same Issue mutatis mutandi in the Plutus, Ledger, Consensus, and Network repositories. Each team will at least need to consider what they want to do and want others to do.

[nfrisby]

Please forgive me if this Issue is just noise. I anticipate that the Plutus Team is the most likely to essentially already have QTAs in place, just under a different name.

Perhaps you can easily discharge this Issue by just pointing (probably the Leader Team) to the relevant documents/benchmarks/etc.

Or, perhaps there is in fact something you'd like from the other teams. For example, maybe we could regularly supply you with a sample of the scripts from the latest few epochs and their execution contexts?

[effectfully]

@nfrisby thanks for opening the issue!

@zliu41 I suppose this one is for you to handle.