Creating a system table after enabling rsgroup feature puts region into RIT

Steps to reproduce

• Enable rsgroup feature
• Enable quota feature which created hbase::quota table
• quota table region will be marked as RIT since the rsgroup for the table is not known

  2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to ENABLING
  2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
  2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on null, set to FAILED_OPEN
  2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a state=OFFLINE, ts=1525977212397, server=null} to {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, server=null}
  2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING to ENABLED
  

• Reason for this issue: 
• system table creation doesn't move the table to the appropriate rs group to which system namespace is assigned to. Need to execute logic similar to what is done in the RSGroupAdminEndpoint for post table creation for user table creation.

Work Around

• Assigning the system table to default rsgroup (or to the rsgroup to which the system namespace has been assigned).
• Manually assigning the region in RIT from the system table