[Survicate] Replace Segment Cloud Mode endpoints

[anna-belka]

Point identify, track, group and auth check requests to the new hv.survicate.com/integrations/partners/segment/* endpoints.

A summary of your pull request, including the what change you're making and why.

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]

Hi @anna-belka the changes look good to me - though I have no way of knowing if they work ;).
Could you add some proof of testing (a couple of screenshots) to the PR description please?
Other than that the PR can be approved.

[anna-belka]

Hi @anna-belka the changes look good to me - though I have no way of knowing if they work ;). Could you add some proof of testing (a couple of screenshots) to the PR description please? Other than that the PR can be approved.

@joe-ayoub-segment
I added screenshots to the description about test result from console.

[joe-ayoub-segment]

Hi @anna-belka the changes look good to me - though I have no way of knowing if they work ;). Could you add some proof of testing (a couple of screenshots) to the PR description please? Other than that the PR can be approved.

@joe-ayoub-segment I added screenshots to the description about test result from console.

Apologies @anna-belka I should have been more expilicit. If possible can you run the code locally and send some test events to your platform - then show the successful delivery somehow.

There is a basic testing tool you can use.

Run this command:
./bin/run serve

You can then type in your credentials and fire off some test Segment payloads.

[anna-belka]

Hi @anna-belka the changes look good to me - though I have no way of knowing if they work ;). Could you add some proof of testing (a couple of screenshots) to the PR description please? Other than that the PR can be approved.

@joe-ayoub-segment I added screenshots to the description about test result from console.

Apologies @anna-belka I should have been more expilicit. If possible can you run the code locally and send some test events to your platform - then show the successful delivery somehow.

There is a basic testing tool you can use.

Run this command: ./bin/run serve

You can then type in your credentials and fire off some test Segment payloads.

@joe-ayoub-segment I did test

Hi @anna-belka the changes look good to me - though I have no way of knowing if they work ;). Could you add some proof of testing (a couple of screenshots) to the PR description please? Other than that the PR can be approved.

@joe-ayoub-segment I added screenshots to the description about test result from console.

Apologies @anna-belka I should have been more expilicit. If possible can you run the code locally and send some test events to your platform - then show the successful delivery somehow.

There is a basic testing tool you can use.

Run this command: ./bin/run serve

You can then type in your credentials and fire off some test Segment payloads.

@joe-ayoub-segment I added screens from Segment Test Event