RSS: Nexus handoff dataset addresses are inconsistent with the initial blueprint

[jgallagher]

RSS's handoff to Nexus includes both the initial blueprint:

omicron/nexus/types/src/internal_api/params.rs

Lines 168 to 169 in 390ac60

	/// Blueprint describing services initialized by RSS.
	pub blueprint: Blueprint,

and a list of datasets to record:

omicron/nexus/types/src/internal_api/params.rs

Lines 177 to 178 in 390ac60

	/// Datasets on the rack which have been provisioned by RSS.
	pub datasets: Vec<DatasetCreateRequest>,

The Blueprint itself also holds a list of datasets. These should be consistent, but currently aren't: the blueprint only populates address for Crucible datasets, but RSS populates the address for any durable dataset associated with a zone:

omicron/sled-agent/src/rack_setup/service.rs

Lines 853 to 871 in 390ac60

	// If any datasets came from a zone, patch their addresses.
	//
	// It would be better if "datasets" was keyed off of a DatasetUuid,
	// but the SeldConfig storing zones does not know about
	// DatasetUuids.
	//
	// Instead, we use the (Zpool, DatasetKind) tuple as a unique
	// identifier for the dataset.
	for zone in &sled_config.zones {
	if let Some(dataset) = zone.zone_type.durable_dataset() {
	let Some(entry) = datasets.get_mut(&(
	dataset.dataset.pool_name.id(),
	dataset.kind.clone(),
	)) else {
	panic!("zone's durable dataset not found");
	};
	entry.request.address = Some(dataset.address.to_string());
	}
	}

At a minimum these should be consistent, but maybe the blueprint has grown to the point where we could remove datasets from the handoff altogether (and let Nexus do what it needs based on the contents of the blueprint)? The same might be true for RackInitializationRequest::{physical_disks,zpools}.