[improvement](colocation) Add a new config to delay the relocation of colocation group

[morningman]

Proposed changes

1. Add a new FE config colocate_group_relocate_delay_second

   The relocation of a colocation group may involve a large number of tablets moving within the cluster.
   Therefore, we should use a more conservative strategy to avoid relocation of colocation groups as much as possible.
   Relocation usually occurs after a BE node goes offline or goes down.
   This config is used to delay the determination of BE node unavailability.
   The default is 30 minutes, i.e., if a BE node recovers within 30 minutes, relocation of the colocation group
   will not be triggered.

2. Change the priority of colocate tablet repair and balance task from HIGH to NORMAL

3. Add a new FE config allow_replica_on_same_host

   If set to true, when creating table, Doris will allow to locate replicas of a tablet
   on same host. And also the tablet repair and balance will be disabled.
   This is only for local test, so that we can deploy multi BE on same host and create table
   with multi replicas.

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Code refactor (Modify the code structure, format the code, etc...)
• Optimization. Including functional usability improvements and performance improvements.
• Dependency. Such as changes related to third-party components.
• Other.

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
• Compiling and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• If these changes need document changes, I have updated the document
• Any dependent changes have been merged

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[yangzhg]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.