Reevaluate Mizar operator design

[clu2xlu]

Revisit operator design for network policy.
PR #338 #328 is dynamically retrieving namespace info and pod info using label, and dynamically calculating tables that will later be passed to daemon
This design is a standalone process, and does not match the design pattern of mizar (e.g. is not utilizing operator store to store network policy object info and its relationship with other network objects). All calculation and data retrieving are done during the create workflow which can cause big latency when cluster size is big.