[BugFix] Fix primary key alter sort key bug

[LiShuMing]

Fixes #30534

std::mismatch is not safe in the old cpp version.

std::mismatch :

1737   template<typename _InputIterator1, typename _InputIterator2,
1738            typename _BinaryPredicate>
1739     _GLIBCXX20_CONSTEXPR
1740     pair<_InputIterator1, _InputIterator2>
1741     __mismatch(_InputIterator1 __first1, _InputIterator1 __last1,
1742                _InputIterator2 __first2, _BinaryPredicate __binary_pred)
1743     {
1744       while (__first1 != __last1 && __binary_pred(__first1, __first2))
1745         {
1746           ++__first1;
1747           ++__first2;
1748         }
1749       return pair<_InputIterator1, _InputIterator2>(__first1, __first2);
1750     }
1751

new version: std::mismatch

1815 #if __cplusplus > 201103L
1816
1817   template<typename _InputIterator1, typename _InputIterator2,
1818            typename _BinaryPredicate>
1819     _GLIBCXX20_CONSTEXPR
1820     pair<_InputIterator1, _InputIterator2>
1821     __mismatch(_InputIterator1 __first1, _InputIterator1 __last1,
1822                _InputIterator2 __first2, _InputIterator2 __last2,
1823                _BinaryPredicate __binary_pred)
1824     {
1825       while (__first1 != __last1 && __first2 != __last2
1826              && __binary_pred(__first1, __first2))
1827         {
1828           ++__first1;
1829           ++__first2;
1830         }
1831       return pair<_InputIterator1, _InputIterator2>(__first1, __first2);
1832     }

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.1
  • 3.0
  • 2.5
  • 2.4

[wanpengfei-git]

[FE Incremental Coverage Report]

😍 pass : 0 / 0 (0%)

[wanpengfei-git]

[BE Incremental Coverage Report]

😞 fail : 7 / 11 (63.64%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	src/storage/schema_change.cpp	7	11	63.64%	[776, 777, 787, 788]

[wanpengfei-git]

@Mergifyio backport branch-3.1

[wanpengfei-git]

@Mergifyio backport branch-3.0

[mergify]

backport branch-3.1

✅ Backports have been created

• #30568 [BugFix] Fix primary key alter sort key bug (backport #30531) has been created for branch branch-3.1

[mergify]

backport branch-3.0

✅ Backports have been created

• #30569 [BugFix] Fix primary key alter sort key bug (backport #30531) has been created for branch branch-3.0 but encountered conflicts