Remove flushing of UVE cache from contrail-analytics.rules

Problem:
  When contrail-collector service is restarted, supervisor stops and then starts the contrail-collector service.
  contrail-analytics-nodemgr receives event "PROCESS_STATE_STOPPED" for process "contrail-collector" when
  supervisor stops the contrail-collector service. The following rule in contrial-analytics.rules causes
  contrail-analytics-nodemgr to flush the UVE cache in redis on receiving the event "PROCESS_STATE_STOPPED".

  {"processname": "contrail-collector", "process_state": "PROCESS_STATE_STOPPED",
   "action": "redis-cli -n 1 eval \"redis.call('flushdb'); redis.log(redis.LOG_NOTICE,'EV_STOP - Nodemgr Flushing Redis UVE')\" 0"}

  There is a race condition between contrail-analytics-nodemgr flushing the UVE cache in redis upon processing
  "PROCESS_STATE_STOPPED" event and contrail-collector updating UVE in redis after restart. i.e.,
  contrail-analytics-nodemgr may flush the UVE cache after contrail-collector writes UVE in redis
  resulting in loss of UVE data.

Fix:
  contrail-collector flushes the UVE cache during initialization. Therefore, remove the rules in contrail-analytics.rules
  whose action triggers flushing of UVE cache in redis.

Impact:
  If contrail-collector service is stopped/entered FATAL state, UVE query would return stale data till contrail-discovery
  removes the collector from publisher list on ttl expiry.

Change-Id: I0fe2cf7e297313e2e061222e78bc3221c6bc5196
Closes-Bug: #1383705
Merge "Remove flushing of UVE cache from contrail-analytics.rules"