[dotnet] Enable ffe for dotnet

[daniel-romano-DD]

Motivation

Changes

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• Anything but tests/ or manifests/ is modified ? I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added, removed or renamed?
  • Get a review from R&P team

[github-actions]

CODEOWNERS have been resolved as:

utils/build/docker/dotnet/weblog/Controllers/FeatureFlagEvaluatorController.cs  @DataDog/apm-dotnet @DataDog/asm-dotnet @DataDog/system-tests-core
manifests/dotnet.yml                                                    @DataDog/apm-dotnet @DataDog/asm-dotnet
utils/build/docker/dotnet/weblog/app.csproj                             @DataDog/apm-dotnet @DataDog/asm-dotnet @DataDog/system-tests-core

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8627086261

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Handle JsonElement defaults for non-string flag types

Here defaultValue is declared as object, so ASP.NET Core’s JSON binding will deserialize booleans/numbers into JsonElement, not bool/int/double. Convert.ToBoolean/ToInt32/ToDouble does not accept JsonElement, so any BOOLEAN/INTEGER/NUMERIC evaluation throws and is caught, returning the default without calling OpenFeature (reason becomes "ERROR"). That means non-string flags can never be evaluated (and exposure events won’t be generated) for requests that send JSON booleans or numbers.

Useful? React with 👍 / 👎.