[I18ONCALL-265] Feature support embed for static data files

[varunkumark1997]

Description

The static data files where supposed to be part of the build process of the service where the sdk is being used. Which lead to build changes on the host service to manually include the files in the build process. Now using "embed" package which go natively solves for building the files during the build step. more info on embed can be found here
Now we are embedding the data directory. Hence no changed in required on the service using this sdk.

Changes Made

List the main changes made in this pull request.

Title	---
JIRA link	I18ONCALL-265
Slack thread (if any)	https://razorpay.slack.com/archives/C04S1K7NXU6/p1728411041703899
Product spec	NA
Tech spec/One-pager	NA
Bundle Size Difference	NA
Fixes Issue	NA

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This change is a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Is your change backward compatible ?
• Tested on major browsers (Chrome, Firefox, Safari, IE) ?
• Tested in a consumer application(s) ?

Additional Notes

Any additional information that would be helpful for the reviewer.

Checklist:

• Add Jira ID(s) in PR title and in the description?
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My code is written in TypeScript and follows the coding standards of the project.
• I have added relevant documentation and updated the README if necessary.
• My commit messages are clear and follow the project's commit message conventions.
• Is any external library added?
• My changes do not introduce any new runtime errors or warnings.
• All relevant unit tests have been added/updated in my PR for the change.
• Any Screenshots (mobile & desktop) required for PR? If yes, have you added the respective screenshots ?
• Any manual dev testing done by you on beta/func environment?
• Reviewer added (SLA 2 days)

Reviewer Checklist

• Sufficient QA/Dev-Testing is done with proof (test cases list)
• Ensure that the change in bundle size falls within the acceptable range.

---

PR Title Format

Format: <type>: <subject>

Types can be as follows:

• feat: (new feature for the user, not a new feature for build script)
• fix: (bug fix for the user, not a fix to a build script)
• docs: (changes to the documentation)
• style: (formatting, missing semi colons, etc; no production code change)
• refactor: (refactoring production code, eg. renaming a variable)
• test: (adding missing tests, refactoring tests; no production code change)
• chore: (updating grunt tasks etc; no production code change)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9651109

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR