Migration error when changing the case of a column AND adding the column to the renaming migration section

[ldhasson]

When changing the case of a column, for example "abc_xyz" to "abc_Xyz", the migration will automatically handle that case. But if someone adds an explicit migration action, Tilda will try to migrate twice.

 ,"migrations":{
      "renames":[
          { "object":"SomeTable", "column":"xyz_abc", "oldNames":["xyz_Abc"]}
       ]
     ,"moves":[
       ]
   }

Tilda, should recognize that there is a "double" migration occurring and flag it as an error: case-changes of column names are handled automatically and shouldn't be handled in the Migrations section.