chore(evaluation-context): Introduce unique schema names

[khvn26]

Thanks for submitting a PR! Please check the boxes below:

• I have added information to docs/ if required so people know about the feature!
• I have filled in the "Changes" section below?
• I have filled in the "How did you test this code" section below?
• I have used a Conventional Commit title for this Pull Request

Changes

In this PR, in order to improve developer experience, we eliminate duplicate schema names in the evaluation context/result schema.

How did you test this code?

Will get tested in Java and NodeJS SDKs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Ignored	Preview		Oct 16, 2025 4:45pm
flagsmith-frontend-preview	Ignored	Preview		Oct 16, 2025 4:45pm
flagsmith-frontend-staging	Ignored	Preview		Oct 16, 2025 4:45pm

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-6168	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-6168	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-frontend:pr-6168	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-api:pr-6168	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-6168	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-6168	Finished ✅	Results ✅