feat: onboard new destination ninetailed

[anantjain45823]

What are the changes introduced in this PR?

Onboard new integration ninetailed destination
Write a brief explainer on your code changes.
It supports identify, track and page calls and requires OrganisationId and environment to generate endpoint and send data and thats what we are taking from the

What is the related Linear task?

Resolves INT-295

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

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 checks got introduced or modified in test suites. Please explain the changes.

N/A

---

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?

• I have executed schemaGenerator tests and updated schema if needed

• Are sensitive fields marked as secret in definition config?

• Is the PR limited to 10 file changes?

• Is the PR limited to one linear task?

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.

[linear]

INT-295 Event stream destination: Ninetailed Integration

Reviewers: shrouti gauravudia

Onboard new Integration Ninetailed as cloud mode and web-sdk destination

References of the requirement (Slack/Notion/PRD doc)

https://rudderlabs.slack.com/archives/D03L204JX8C/p1691437826072369

---

• If there are any design-related discussions or changes that require a design review, please link the here.

• Design/Research doc: https://www.notion.so/rudderstacks/Ninetailed-b0a34806a24e44c9a4653b74c7972cf6?pvs=4

• Test cases doc:https://www.notion.so/rudderstacks/9c70f4d326d24fb298d3fdb56618720e?v=3695c399f4824af5889c90b55746ef68&pvs=4

---

• Changes tested locally as well as in dev/staging environments.
• Existing test cases updated for the new feature.
• Has the task been checked against the design request questionnaire - https://www.notion.so/rudderstacks/When-to-ask-for-a-design-review-a3534d5e4f5f4fcb989847ca9cd96189

---

• The Slack link for the respective thread is attached.
• Docs card attached.
• GitHub PR is attached to the task.
• Release label attached to the task.
• The project associated with the task is linked, if any.
• Document the monitoring steps here

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (2bfdb1d) to head (dfa3f88).
Report is 58 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff            @@
##           develop     #1211   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           53        53           
  Branches         7         7           
=========================================
  Hits            53        53           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.