[AMORO-1865]build a rule of relationship between table and resource group

[Aireed]

Why are the changes needed?

Close #1865.

Brief change log

• Front-end:
  • Configure by adding rules in the properties of optimize-group with key 'match.rules'

• Backend:

  • 1. When creating a group, rule conflict detection will be performed.
       And traverse the table corresponding to the catalog default value of the current optimize-group to see if it matches the current rule and assign the value.
  • 2. When updating the optimize-group rules, rule conflict detection will be performed.
    • 1. First, the table under the current rule will be judged. If the rule no longer matches after the rule is changed, the default group of the catalog to which the table belongs will be used.
    • 2. Traverse the table corresponding to the catalog default value of the current optimize-group to see if it matches the current rule and assign the value.
  • 3. when deleting the group
    • 1. Configure the tables under the group to the default group of the catalog to which they belong.
         When the group of the above table is changed, the tableConfigureChange responsibility chain call of the table will be triggered.
  • 4. When synchronizing the external catalog, the group will be automatically matched according to regular rules.
  • 5. TableRuntimeRefreshExecutor no longer pays attention to optimize-group when refreshing.

• Special note
  We support manually adding the table name to the rules of a group, which is equivalent to the original manual configuration of the group. Because in our practice, there are some situations that require manual specification.

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[XBaith]

Is this method nessessary? How about invoke getIdentifier().toString() to get full name?

[Aireed]

Is this method nessessary? How about invoke getIdentifier().toString() to get full name?

getIdentifier().toString() returns TableIdentifier[catalog.db.table], So it's not suitable.

[XBaith]

Okay, It not org.apache.amoro.table.TableIdentifier. I perfer use the following method, WDYT?

  public org.apache.amoro.table.TableIdentifier getTableIdentifier() {
    return org.apache.amoro.table.TableIdentifier.of(catalog, database, tableName);
  }

[XBaith]

tableIdentifier.toString()

[baiyangtx]

This implementation method will be contrary to the current advanced issue of splitting the rest service and the scheduling service. It makes the update of the group have to occur at the master node.