Issue 1542/refactor EVENTS into hooks

[rebecarubio]

Description

This PR refactors all Event Models into hooks

Changes

• Removes EventDataModel, EventTypesModel, EventsModel and LocationsModel
• Removes ZUISpeedDial and /TaskList
• Adds useAllEvents (will be removed when mergin Campaigns hook)
• Adds useDuplicateEvent
• Adds useEventContact
• Adds useEvent and useEventMutations
• Adds useEventLocations and useEventLocationsMutations
• Adds useEventParticipants and useEventParticipantsMutations
• Adds useEventState
• Adds useEventTypes
• Adds useEventsMutations
• Adds useParallelEvents
• Adds useParticipantsStatus
• Adds useRelatedEvents
• Adds useCreateType
• Adds useCreateEvent
• Changes all references from old event models to the new hooks and implements relevant changes

Notes to reviewer

Repo file will be removed in another PR.
useAllEvents hook is used only by AllCampaignsSummaryPage and it will be removed after merge Campaigns refactor PR #1586

Related issues

Part of issue 1542

[richardolsson]

Amazing work on this major refactor! I think the code looks mostly great. I did find some opportunities for optimization (loading only necessary events instead of loading all of them) and also some design decisions that I don't fully agree with.

I especially think we need as a team to talk about:

• Should mutation hooks take the ID of the object they're meant to mutate in the hook, or in the mutation functions? (I prefer the former)
• Should hooks that load data generally return a future or an object containing a future (and if so, should it be called e.g. eventFuture or just event)?
• Where do we put "create" actions, i.e. mutations that create a new object on the server? They don't quite fit in the normal mutation hooks (which are for a single, already existing object) nor in the plural hooks, because we don't want to retrieve data before creating. Maybe a separate hook, e.g. useCreateEventType() etc?

[richardolsson]

Awesome work on this massive PR! It's very big, so I might have missed something, but the code looks good to me. I haven't tested it, but if it's working as expected, I think it can be merged.