[IOTDB-1260] optimize time_range query because syncMetaLeader

[wangchao316]

1. The syncMetaLeader in CMManager.getAllpath accounts for 10 percent of the performance of the query.
2. The syncMetaLeader has been invoked in ClusterPhysicalGenerator.transformToPhysicalPlan.
3. The possibility of metadata change is small and cannot be the bottleneck of query.
   Solution:
   remove syncMetaLeader in CMManager.getAllpath.
   test result:
   Time_Range AVG before optimization: 139.38
   Time_Ranger AVG after optimization: 110.19

[wangchao316]

@LebronAl @neuyilan @mychaow @jt2594838 hi, could you please review?
Thanks

[OneSizeFitsQuorum]

LGTM~
For one query request, we can at least optimize to one syncMetaLeader per query, maybe there are still some redundant places now.

[wangchao316]

LGTM~
For one query request, we can at least optimize to one syncMetaLeader per query, maybe there are still some redundant places now.

yes , I will I'll look elsewhere.

[neuyilan]

LGTM