Decrease size of serialized ParsingQueueTask The RevisionCreatedListener.Event contained a whole lot of data that we don't need. The footprint of one ParsingQueueTask with the Event was ~22k which is unnecessarily large. Storing the vital information in the dto PatchsetCreationData instead significantly decreases the storage footprint of a ParsingQueueTask. Solves: Jira GER-1715 Change-Id: Ia463c34d9235f8208d376d78f0c68d1dba595bd8