feat: implement free trial conversion optimization with A/B testing (…

[Eromosele0110]

…#558)

Pull Request Checklist

Quality Gates (All must pass before merge)

• Lint: Code passes ESLint and Prettier checks
• Type Check: TypeScript compilation succeeds
• Tests: All tests pass
• Build: Project builds successfully
• Rust Format: Smart contract formatting is correct
• Rust Clippy: Smart contract linting passes
• Rust Tests: All smart contract tests pass
• Rust Build: Smart contracts compile successfully

Additional Requirements

• New code has appropriate TypeScript types
• No hardcoded secrets or credentials
• New features have corresponding tests
• Documentation updated if needed

Reviewers

• At least 1 approval required for merge
• All CI checks must be green

---

This PR will not be mergeable until all quality gates pass.
close #558

[drips-wave]

@Eromosele0110 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
34266369	Triggered	Generic Password	283c56e	backend/config/tests/redis.test.ts	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}