Support detection of moved code in git blame (-M and -C flags)

[olejorgenb]

(Also pointed out here: #10771 (comment))

Many IDE's support toggling this dynamically which would be ideal, but a configuration option might be enough.

       -M[<num>]
           Detect moved or copied lines within a file. When a commit moves or copies a block of lines (e.g. the original
           file has A and then B, and the commit changes it to B and then A), the traditional blame algorithm notices only
           half of the movement and typically blames the lines that were moved up (i.e. B) to the parent and assigns blame
           to the lines that were moved down (i.e. A) to the child commit. With this option, both groups of lines are
           blamed on the parent by running extra passes of inspection.

           <num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as
           moving/copying within a file for it to associate those lines with the parent commit. The default value is 20.

       -C[<num>]
           In addition to -M, detect lines moved or copied from other files that were modified in the same commit. This is
           useful when you reorganize your program and move code around across files. When this option is given twice, the
           command additionally looks for copies from other files in the commit that creates the file. When this option is
           given three times, the command additionally looks for copies from other files in any commit.

           <num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as
           moving/copying between files for it to associate those lines with the parent commit. And the default value is
           40. If there are more than one -C options given, the <num> argument of the last -C will take effect.

[olejorgenb]

Since Zed already parse the output of git blame I assume simply routing the option to

zed/crates/git/src/blame.rs

Line 67 in ede3b1d

async fn run_git_blame(

would work.