Move Noop, MakeTuple, UnpackTuple, Tag to prelude extension

[ss2165]

Requires #787

[acl-cqc]

I think this can be done without #787 by defining custom binary compute_signature functions. This just moves code around (i.e. the code that currently compute signature of these ops gets moved into an extension), with I suspect a substantial increase in boilerplate. OTOH it makes the API more uniform.

As a side benefit it also brings fields such as

hugr/hugr/src/ops/leaf.rs

Line 18 in 0bab478

pub ty: Type,

and

hugr/hugr/src/ops/leaf.rs

Line 32 in 0bab478

pub tys: TypeRow,

into scope for this check:

hugr/hugr/src/hugr/validate.rs

Lines 544 to 549 in 0bab478

	// Check TypeArgs are valid, and if we can, fit the declared TypeParams
	match resolved {
	CustomOp::Extension(exten) => exten
	.def()
	.validate_args(exten.args(), self.extension_registry, var_decls)
	.map_err(|cause| ValidationError::SignatureError { node, cause })?,

....which "feels right", but (for these ops) doesn't catch anything that we wouldn't anyway in

hugr/hugr/src/hugr/validate.rs

Lines 222 to 223 in 0bab478

	self.validate_port_kind(&port_kind, var_decls)
	.map_err(|cause| ValidationError::SignatureError { node, cause })?;

.

[acl-cqc]

We've done #787, so we can do this now without any "custom binary" code for compute_signature. I think we should.

Lift similarly (although Lift has limited lifespan, should disappear following #919)

CallIndirect similarly (this should go in the Tierkreis extension, not prelude).