Handle ticket merges

[tom-coward]

Handle the changing of the resource ticket_id key if necessary on ticket merge.

[tom-coward]

Need to consider best way of handling this situation. It's possible that the merged tickets (of which there could theoretically be an unlimited amount) may each already be associated to different resources, so some form of confirmation of which resource to associate to the one ticket after merge would be required.