feat: add the missing presets to pipedrive destination defined in actions prop

[abusarah-tech]

This PR intends to add the missing presets to the Pipedrive destination that are already available in the actions property

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

Security Review

Please ensure sensitive data is properly protected in your integration.

• Reviewed all field definitions for sensitive data (API keys, tokens, passwords, client secrets) and confirmed they use type: 'password'

New Destination Checklist

• Extracted all action API versions to verioning-info.ts file. example

[joe-ayoub-segment]

There is already a preset subscribing to type = 'identify'. This would cause issues for customers as it would create and update a deal and create or update a Person from the same identify event.

[abusarah-tech]

According to the documentation the default trigger for Person and Lead is type = 'identify'

[joe-ayoub-segment]

Hi @abusarah-tech thanks for the PR.
Can you please confirm your identity by emailing jayoub@twilio.com from your work email please?
Do you work for Pipedrive?

We've deliberately left the number of presets for this integration low, as there's no natural Segment event specification which matche many of the CRM activities this integration handles.

[abusarah-tech]

Hi @abusarah-tech thanks for the PR. Can you please confirm your identity by emailing jayoub@twilio.com from your work email please? Do you work for Pipedrive?

We've deliberately left the number of presets for this integration low, as there's no natural Segment event specification which matche many of the CRM activities this integration handles.

Hi, thanks for your update! I do not work for Pipedrive. But the demand came from customers using PostHog that want to sync the leads and deals as mentioned in this issue (PostHog/posthog#44639)

This is my initiative to extend the presets because they rely on them to provide the options for syncing data to PostHog and at the moment they can only cover Person, Organization and Activity.