ddl, parser: fix the DDL job version using issue (#47915)

[ti-chi-bot]

This is an automated cherry-pick of #47915

What problem does this PR solve?

Issue Number: close #47912 (Fix this issue on master), close #46306 (Fix this issue on v7.5)

Problem Summary:
After #3993, we using job.Version like

	if job.Version <= currentVersion {
		err = w.delRangeManager.addDelRangeJob(ctx, job)
	} else {
		err = dbterror.ErrInvalidDDLJobVersion.GenWithStackByArgs(job.Version, currentVersion)
	}

So, when we add the currentVersion value(#47818) and have two versions TiDB has an issue.

What is changed and how it works?

Use ReorgMeta's version instead of Job's.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

  • Case 1
    deploy v7.1.0 cluster with 2 tidb.
    Then upgrade this cluster to master one by one.
    Result: After this PR, upgrade successfully.

  • Case 2(Manual test in pkg/ddl: fix an issue where endkey usage issues caused index loss (#47818) #47884 )
    deploy v7.1.1+ cluster with 1 tidb
    set @@global.tidb_ddl_enable_fast_reorg = 0;
    Create a table and import 3.5 million rows.
    Do alter table t add index idx(a, b);, and when it backfills 700,000+ indexes, kill the cluster.
    Then upgrade this cluster to master.
    After upgrading successfully, do admin check index t idx
    Result: we get Query OK.

• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[zimulala]

/retest-required

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tangenta, wjhuang2016

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [tangenta,wjhuang2016]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2023-10-24 02:06:19.304113862 +0000 UTC m=+2313976.891223991: ☑️ agreed by tangenta.
• 2023-10-25 04:18:42.369123738 +0000 UTC m=+2408319.956233883: ☑️ agreed by wjhuang2016.