`redundant_clone` could also fire when the containing object will be dropped

What it does

Consider this code from Zed:

    pub fn append(&mut self, rope: Rope) {
        // ....
        self.chunks.append(rope.chunks.clone(), ());
        self.check_invariants();
    }

rope is passed by value and dropped at the end of the function. I think we can eliminate the clone and just consume rope.chunks.

Clippy doesn't warn about this even with clippy::redundant_clones turned on, I think because it's a more complex situation of consuming one field from a struct.

Start with the redundant_clones lint entry point and its existing tests, using the Rust example in Zed's crates/rope/src/rope.rs as the behavioral case. Determine how the lint handles consuming a field from a by-value parameter, then add coverage showing that the clone is unnecessary when the containing object is dropped.