Overwriting contract build parameters

[pmikolajczyk41]

drink::test macro builds all required contracts, but uses common build profile for them, possibly overwriting some parameters (like optimization passes). We might want to enable some customization, e.g. through contract exclusion from this build procedure

I'm wondering - some of these params are definable in Cargo.toml - especially for the root package - and here we're "overwriting" them. That's probably fine since we are "optimising for drink!" but just something to be aware of.

Originally posted by @deuszx in https://github.com/Cardinal-Cryptography/drink/pull/70#discussion_r1368350504