Refactoring to reorder tuple elements

[jnm2]

The scope of the change should be the same as the scope that a tuple element rename would have, whenever that is decided: https://github.com/dotnet/roslyn/issues/14115

Example

I have this code, with three callers. I decided it's confusing on the call side to have the URLs last, so I want to move each string Url tuple elements to be the first element. It would be nice to be able to invoke a refactoring for each of the two moves which would fix up the callers and also the tuple usages within this method:

public static void WriteLinkPanel(
    Action<string> writeLine,
    (string Display, string Url) fileLink,
    string webAccessUrl = null,
    (string Display, string Url, string AssemblyName)? projectLink = null)

[JoeRobich]

Proposal from design meeting:

• Add new refactoring "Change Tuple Signature…" which will display a dialog similar to the Change Signature dialog.
• Initially it may only allow elements to be reordered but we can see this dialog growing to expose add, remove, rename, and update modifiers for tuple elements.
• Ability to specify scope like the convert tuple to struct refactoring.
• Ability to require matching element names to further narrow scope.