Enhance Stripe Plugin to Support Localized Order Confirmation Emails

[HerclasNido]

Description

This PR introduces updates to the Stripe Plugin to enable sending localized order confirmation emails based on the customer's language, rather than defaulting to English. Here's a summary of the changes:

• Added languageCode to Stripe Metadata: When creating a paymentIntent, the languageCode is now included in the metadata along with channelToken, orderId, and orderCode.
• Localized Context for Webhook Requests: When processing Stripe webhook requests at the /payments/stripe endpoint, the createContext() function now uses the languageCode from the metadata to set the context's language. This replaces the previous behavior of defaulting to LanguageCode.en.

These changes allow the languageCode passed during the createStripePaymentIntent mutation to be accessible in the EmailTemplateLoader for the "order-confirmation" event, ensuring emails are sent in the correct language.

Breaking changes

No breaking change

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

This is my first PR, so I’m not entirely sure if everything is correct. I’d appreciate any feedback to help me improve! 😊

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Dec 27, 2024 2:23am

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[HerclasNido]

I have read the CLA Document and I hereby sign the CLA

[michaelbromley]

Hi, thanks for this PR! It all looks good to me. The only thing I'd like you to change is to remove the package-lock.json file from the PR since I guess that should not have changed?