Emit correct warning for duplicate instrument conflict

[MrAlias]

From the specification:

The emitted warning SHOULD include information for the user on how to resolve the conflict, if possible.

1. If the potential conflict involves multiple description properties, setting the description through a configured View SHOULD avoid the warning.
2. If the potential conflict involves instruments that can be distinguished by a supported View selector (e.g., instrument type) a renaming View recipe SHOULD be included in the warning.
3. Otherwise (e.g., use of multiple units), the SDK SHOULD pass through the data by reporting both Metric objects and emit a generic warning describing the duplicate instrument registration.

The first two items are not done.

opentelemetry-go/sdk/metric/pipeline.go

Lines 357 to 366 in 135c64f

	global.Info(
	"duplicate metric stream definitions",
	"names", fmt.Sprintf("%q, %q", existing.Name, id.Name),
	"descriptions", fmt.Sprintf("%q, %q", existing.Description, id.Description),
	"units", fmt.Sprintf("%s, %s", existing.Unit, id.Unit),
	"numbers", fmt.Sprintf("%s, %s", existing.Number, id.Number),
	"aggregations", fmt.Sprintf("%s, %s", existing.Aggregation, id.Aggregation),
	"monotonics", fmt.Sprintf("%t, %t", existing.Monotonic, id.Monotonic),
	"temporalities", fmt.Sprintf("%s, %s", existing.Temporality.String(), id.Temporality.String()),
	)

Originally posted by @MrAlias in #3653 (comment)