Allow significantChangeHash returned from Broker::parseEventInfo to also be based on property parameters

[KristofferFM]

Currently, the hash is based on a configurable set of property values. Under some circumstances, it might be useful to also look at property parameters?

For instance, if an organizer changes the value of the PARTSTAT property parameter, it might justify sending out new iTip messages via email to attendees.