Add Vitally destination

[jason-vitally]

Description of the change

Adds Vitally as a new destination. The only transformation needed is:

• attach API key to the authorization header
• drop events that aren't group, identify and track

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issues

config-generator
transformer
rudderstack-docs

Development

• Lint rules pass locally
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
• "Ready for review" label attached to the PR and reviewers mentioned in a comment
• Changes have been reviewed by at least one other engineer
• Issue from task tracker has a link to this pull request

[github-actions]

This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.

[jason-vitally]

This PR is considered to be stale. It has been open 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.

Commenting to keep this PR from getting stale. I spoke with @ItsSudip in a shared Slack about these PRs and they said this should be reviewed shortly

[github-actions]

This PR is considered to be stale. It has been open for 20 days with no further activity thus it is going to be closed in 7 days. To avoid such a case please consider removing the stale label manually or add a comment to the PR.

[ItsSudip]

Hey @jason-vitally as we have released this integration through another pr we are closing this. You can follow this link for documentation details and this link for the repo.