[BugFix] Disable duplicate sort key when creating table (backport #43206)

[mergify]

Why I'm doing:

If we create table with duplicate sort key columns, BE maybe crash. For example:

1. We create a primary key table with duplicate sort key column (k1,v1,v1).
2. In vertical compaction, we will first create a schema k1,v1,v1 to read the sort key columns from segment data.
3. When we create segment_iterator, we will create column_iterator for each column according to the column id. However, the two columns v1 has the same column id, so we only create one column iterator.
4. During read data, we will generate a chunk with three columns and read data column by column. But the two columns v1 will use the same column iterator to read data and the offset is inconsistent with column k1 and it may cause the rows in different columns in a chunk are inconsistent and this may cause BE crash.

What I'm doing:

Disable duplicate sort key when creating table.

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
• This is a backport pr

Bugfix cherry-pick branch check:

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

---

This is an automatic backport of pull request #43206 done by [Mergify](https://mergify.com). ## Why I'm doing: If we create table with duplicate sort key columns, BE maybe crash. For example: 1. We create a primary key table with duplicate sort key column (k1,v1,v1). 2. In vertical compaction, we will first create a schema `k1,v1,v1` to read the sort key columns from segment data. 3. When we create `segment_iterator`, we will create `column_iterator` for each column according to the column id. However, the two columns `v1` has the same column id, so we only create one column iterator. 4. During read data, we will generate a chunk with three columns and read data column by column. But the two columns `v1` will use the same column iterator to read data and the offset is inconsistent with column `k1` and it may cause the rows in different columns in a chunk are inconsistent and this may cause BE crash.

What I'm doing:

Disable duplicate sort key when creating table.

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
• This is a backport pr

[mergify]

Cherry-pick of 5312180 has failed:

On branch mergify/bp/branch-2.5/pr-43206
Your branch is up to date with 'origin/branch-2.5'.

You are currently cherry-picking commit 53121805f2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   test/sql/test_sort_key/R/test_sort_key_pri_tbl
	new file:   test/sql/test_sort_key/T/test_sort_key_pri_tbl

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   fe/fe-core/src/main/java/com/starrocks/server/OlapTableFactory.java
	deleted by us:   test/conf/sr.conf
	deleted by us:   test/sql/test_sort_key/R/test_sort_key_agg_tbl
	deleted by us:   test/sql/test_sort_key/R/test_sort_key_dup_tbl
	deleted by us:   test/sql/test_sort_key/R/test_sort_key_uni_tbl
	deleted by us:   test/sql/test_sort_key/T/test_sort_key_agg_tbl
	deleted by us:   test/sql/test_sort_key/T/test_sort_key_dup_tbl
	deleted by us:   test/sql/test_sort_key/T/test_sort_key_uni_tbl

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr