Optimisation level multiplier for bytecode size

[aakoshh]

Problem

Followup for #6505

Add some kind of parameter similar to --inliner-aggressiveness, which would tell the compiler how much of a potential increase in Brillig bytecode size it can accept when unrolling loops. See #6505 (comment)

Happy Case

See #6505 (comment)

Workaround

None

Workaround Description

No response

Additional Context

No response

Project Impact

Nice-to-have

Blocker Context

There was an increase in bytecode size in the Keccak256 test, which would be nice to avoid.

Would you like to submit a PR for this Issue?

None

Support Needs

No response