drop column have 4 args if jobs created by new node instead of 2 as old node does

[D3Hunter]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

• in old version we have 2 param, and append the other 2 at runtime, the other 2 are used for deleting kv ranges that's useless
  

  tidb/pkg/ddl/ddl_api.go

  Line 5378 in 945d07c

  Args: []any{colName, spec.IfExists},

• but in new version we set 4 param at first when the job is in v1
  

  tidb/pkg/meta/model/job_args.go

  Line 776 in 6463db6

  return []any{a.Col.Name, a.IgnoreExistenceErr, a.IndexIDs, a.PartitionIDs}

• if the job is submitted by new version node, but it's run by old version tidb(it's possible when there are multiple owner during upgrade, see modify column keeps in writing temp column to tableinfo during upgrade from 8.1 -> 8.5, when there are multiple owners #58843), the appended args will take no effects, this will cause the data range not deleted automatically. we don't have drop column during upgrade right now, so it's ok, so we mark it as minor

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

master