Redundant clone suggestion in move error

[estebank]

We currently emit two suggestions to .clone() in some move errors:

rust/tests/ui/suggestions/option-content-move.stderr

Lines 12 to 19 in 35f1109

	help: you can `clone` the value and consume it, but this might not be your desired behavior
	|
	LL | if <Option<String> as Clone>::clone(&selection.1).unwrap().contains(selection.0) {
	| ++++++++++++++++++++++++++++++++++ +
	help: consider cloning the value if the performance cost is acceptable
	|
	LL | if selection.1.clone().unwrap().contains(selection.0) {
	| ++++++++

We should emit only one of the two.

[yuk1ty]

@rustbot claim