feat: identify and track for loops

[danrowden]

What are the changes introduced in this PR?

Added Identify and Track events for new Loops destination.

Current status: This is a first go at implementing a new destination, so it's considered WIP until checked by someone more familiar with Rudderstack.

What is the related Linear task?

None

Please explain the objectives of your changes below

New destination for Loops that lets users sync contacts into Loops and sent events to Loops (to trigger email sending).

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new generic utility introduced or modified. Please explain the changes.

N/A

Any technical or performance related pointers to consider with the change?

N/A

@coderabbitai review

---

Developer checklist

• My code follows the style guidelines of this project

• No breaking changes are being introduced.

• All related docs linked with the PR?

• All changes manually tested?

• Any documentation changes needed with this change?

• Is the PR limited to 10 file changes?

• Is the PR limited to one linear task?

• Are relevant unit and component test-cases added in new readability format?

Reviewer checklist

• Is the type of change in the PR title appropriate as per the changes?

• Verified that there are no credentials or confidential data exposed with the changes.

[contributor-support]

Thank you @danrowden for contributing this PR.
Please sign the Contributor License Agreement (CLA) before merging.