Redesign hierarchy of feature rules

[terrymanu]

Currently, ShardingSphere uses order to control the creation and decoration of Feature Rules, which leads to mutual influence and dependence among different rules, and is not conducive to the plug-in design of rules.

The new ShardingSphere Feature Rule scheme divides rules into hierarchical levels. Rules of different levels are constructed in the order of their levels, and rules of the same level do not need to be distinguished in order. The rule hierarchy is divided as follows:

• MetaRule
  • Resource
    • Node(Instance)
      • DatabaseDiscoveryRule（Traffic）
    • Unit(DataSource)
      • ReadwriteSplitRule（Traffic）
  • Table
    • ShardingRule（Data + Traffic）
    • ShadowRule（Traffic）
  • Column
    • EncryptRule（Data）
    • MaskRule（Data）
• OperationRule
  • AuthorityRule

Construct order:
Resource -> Table -> Column

Execute order:
Table ->
-- Traffic: Resource
-- Data: Column

[boyjoy1127]

Will this issue be completed before June 15 which is the final date of version 5.4.0?