add ProcessUpdateEvent trigger to controll whether sent the event to the recivers when the event is update

[wuzhuoquan]

if an event occur many times, It will only update the event fields like count and lastTimestamp.
By default kubernetes-event-exporter will ignore the eventUpdate and will not sent to the recivers.
If you Don't want to miss every event,you can use trigger processUpdateEvent to controll whether sent the event to the recivers.

[mustafaakin]

I have conflicting views on this. While agree this is needed, it's not applicable for all sinks, that are append only and would result in huge duplicates because of image cannot be pulled x1000 times. Instead it should be configured sink level

[wuzhuoquan]

I have conflicting views on this. While agree this is needed, it's not applicable for all sinks, that are append only and would result in huge duplicates because of image cannot be pulled x1000 times. Instead it should be configured sink level

So this PR only set the trigger processUpdateEvent to controller whether sent all events to the recivers. By default is false, means will not sent the update event to sinks, but sometimes the user want to sent all event to sinks, then they can set it to true.

This PR only provide a option for the user to make it possible.

[mustafaakin]

Problem with this contribution is that configuration should be local to each sink. It does not matter that default is false. If it's enabled to true, it sends changes to all sinks regardless of it makes sense or not. I want ability to send regular messages to one sink (Opsgenie), and all updates to another (Kafka)

Additionally, the sinks need to be aware of ID generation so the sinks can update the data instead of growing the underlying storage.

Therefore, unless those changes are made, I can't merge this PR.