RedundantInputAssignment rule?

[a-frantz]

From the WDL v1.1.1 spec:

If a call input has the same name as a declaration from the current scope, the name of the input may appear alone (without an expression) to implicitly bind the value of that declaration. For example, if a workflow and task both have inputs x and z of the same types, then call mytask {input: x, y=b, z} is equivalent to call mytask {input: x=x, y=b, z=z}.

I suggest a rule that requires the shorthand form when it's possible. e.g. { input: bam = bam } would result in a lint note suggesting the simplification { input: bam }.