struct fields that can be reordered to avoid clones during struct init

What it does

Check for data that is cloned into struct field because a move would prevent the data being used in another field (by reference).
Suggest to change the field order to remove the clone

Advantage

less clones, more 🚀

Drawbacks

No response

Example

struct S {
    A: String,
    B: String,
}

pub fn main() {
    let x = String::from("hello");

    let s = S {
        A: x.clone(), // :( 
        B: format!("{}", x),
    };
}

Could be written as:

struct S {
    A: String,
    B: String,
}

pub fn main() {
    let x = String::from("hello");

    let s = S {
        B: format!("{}", x),
        A: x, // :) 
    };
}

Start from the struct initialization examples in the issue and examine how field evaluation and moves make the clone unnecessary. Determine the cases where reordering fields is safe, then add a lint suggestion and tests covering the shown clone-versus-move pattern.