Use a tracing-based API for debugging and profiling constraints

[Pratyush]

Blocked on #186

PR #186 improved the ergonomics of writing constraints and gadgets, but regressed the ergonomics of profiling and debugging constraints. This PR attempts to rectify that by moving to an API based on the tracing crate. To enter a namespace, simply annotate the relevant function with the tracing::instrument attribute, with target = "r1cs":

#[tracing::instrument(target = "r1cs")]
fn some_gadget(...) -> Something {
	///...
}

See r1cs_std for examples.

Closes #250