fix: add support for EU region specific script

[anantjain45823]

PR Description

We are not incorporating src in customerIo according to region instead using non-euone only as constant.
This PR is fixing this issue by incorporating eu region specific src as well

Notion ticket

Ticket link

Screenshots

Please add screenshots for any new features or UI bug fixes for the following browsers -

• Chrome

• Firefox

• Safari

Security

• The code changed/added as part of this pull request won't create any security issues with how the software is being used.

[github-actions]

size-limit report 📦

Name	Size (Base)	Size (Current)	Size Limit	Status
Core - CDN	36.56 KB	36.56 KB (0%)	39.94 KB	✅
All Integrations - CDN	426.58 KB	426.61 KB (+0.01% ▲)	433.11 KB	✅
Core - NPM	36.51 KB	36.51 KB (0%)	39.84 KB	✅
Service Worker - NPM	27.8 KB	27.8 KB (0%)	28.03 KB	✅

[linear]

INT-162 CustomerIO Destination Gaps

There are certain gaps in our customerIo implementation which are listed as below

1. we are not prioritizing timestamp over original timestamp at all places.

2. We can take leverage of cio_id(given to user by cutomerIo) for updating the user, grouping the user or mapping/deleting some device and even for alias call which we are not doing currently.

3. For group call if there are no identifiers present then also we seem to be making the call which is not correct since the data is missing we should through instrumentation error from transformer itself before sending the request to customerIo.

   https://customer.io/docs/api/track/#operation/identify

4. Prevent bugsnag issue by making use of optional parameters or validation layer

5. Enable EU vs US region server configuration in UI (cc: yashasvi )

https://www.notion.so/rudderstacks/CustomerIo-Gaps-Research-Spec-f010ca9b44fb483fab57f876213becfe?pvs=4

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication