feat: zapier integration

[kylemcshea]

Link to ticket

Please add a link to the GitHub issue being addressed by this change.

Developer Guide
https://docs.google.com/document/d/1HWamnw-ebKEM60mPL8sLQYJPW8inJHF2a-RSXnIxG5c/edit#heading=h.7jl8tl5k1raa

Description

Please include a short description of the suggested change and the reasoning behind the approach you have chosen.

The intent of this PR is to add the following pieces for a zapier integration:

Triggers

• New Todo
• Todo Updated (fields in particular: status, assignee, due date, title, description, sprint, milestone)
• New Milestone (milestones are just todos with the type “milestone”)
• Milestone updated
• New Goal
• Goal Updated (objective, metrics start, current, goal)
• New Idea
• Idea Updated
• New Comment (could be anywhere in the system)
• New Timesheet entry
• Timesheet entry updated
• New Project
• Project details updated

Actions

• Create Todo
• Update Todo (not sure if we want to be specific in terms of updates, see below)

Update Todo Status
Update Assignee
Update Milestone

• Create Milestone
• Create Timesheet Entry

This was done by utilizing mostly service layer methods that with the proper parameters can be utilized.

With that being said not all service layer methods needed to make these zapier interactions possible are made.

One thing to denote - when checking for an updated artifact since Zapier uses id to index objects in a list, what we must do is append it with its last_updated dateTime string so that we can detect any differences in the id indices.

So we would end up modifying our returned id to be like {id}-{modified_date}

Here is where I derived this decision from:
https://community.zapier.com/how-do-i-3/polling-an-api-for-updated-records-not-just-new-ones-1165

Screenshot of the result

If your change affects the user interface, you should include a screenshot of the result with the pull request.

Checklist

• My code passes all test cases.
• My code passes our static analysis suite.
• My code passes our continuous integration process.

If your code does not pass the requirements on the checklist, you should add a comment explaining why this change
should be exempt from the list.

Additional comments or questions

If you have any further comments or questions for the reviewer, please add them here.

New Goal will be completed in a seperate PR as the canvas -> canvas item relation makes that task not exactly straight forward

[CLAassistant]

All committers have signed the CLA.