[Hubspot] Update hubspot custom event action to handle numeric strings

[harsh-joshi99]

In HubSpot custom event actions, numeric string values in properties were being inferred as numbers. When the corresponding property in HubSpot was actually defined as a string, this resulted in schema mismatch errors.

This PR updates the inference logic to correctly handle numeric strings. If a value is inferred as a number but the property type in HubSpot is a string, we convert the value back to a string before sending it.

JIRA -> https://twilio-engineering.atlassian.net/browse/STRATCONN-6467

Testing

Testing Document

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'

[codecov]

Codecov Report

❌ Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 80.27%. Comparing base (01bf1df) to head (943227a).

Files with missing lines	Patch %	Lines
...mEvent/functions/hubspot-event-schema-functions.ts	85.71%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3523      +/-   ##
==========================================
+ Coverage   80.25%   80.27%   +0.02%     
==========================================
  Files        1275     1275              
  Lines       23484    23499      +15     
  Branches     4696     4701       +5     
==========================================
+ Hits        18847    18864      +17     
+ Misses       3762     3761       -1     
+ Partials      875      874       -1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR fixes a schema mismatch issue in the HubSpot custom event action where numeric string values (e.g., "123") were being inferred as numbers during schema creation, but HubSpot had the corresponding properties defined as strings, causing validation errors.

Changes:

• Adds logic to detect when a property is inferred as a number but HubSpot expects a string, and converts the value to a string before sending
• Implements conversion for both cache hit scenarios (using cached schema) and cache miss scenarios (fetching from HubSpot)
• Adds comprehensive test coverage for various numeric string scenarios including single properties, multiple properties, partial matches, and verification that actual numbers remain unconverted

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
types.ts	Adds numericStrings array to SchemaDiff type to track properties requiring conversion
index.ts	Adds call to convertNumericStrings for cache hits and passes payload to getSchemaFromHubspot for conversion
hubspot-event-schema-functions.ts	Implements numeric-to-string conversion logic when fetching schema from HubSpot, distinguishing string mismatches from other type mismatches
cache-functions.ts	Adds numericStrings tracking in compareSchemas and implements convertNumericStrings utility function
index.test.ts	Adds comprehensive test suite covering cache hits, cache misses, multiple numeric strings, partial property matches, and validation that actual numbers aren't converted

[joe-ayoub-segment]

PR reviewed.

[joe-ayoub-segment]

See comment

[harsh-joshi99]

#3555