fix: expose ValueJsonConverter for generator support and add JsonSourceGenerator test cases

[WeihanLi]

This PR

• Expose ValueJsonConverter
• Add JsonSourceGenerator serialize test cases
• Enable AOT analyzer and let sample AOT safe

Related Issues

Fixes #536

Notes

We needed to exclude diagnostics to work around dotnet-format issue, see dotnet/sdk#50012

Follow-up Tasks

How to test

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.48%. Comparing base (c0eb12a) to head (f4257b8).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #537   +/-   ##
=======================================
  Coverage   88.48%   88.48%           
=======================================
  Files          50       50           
  Lines        2102     2102           
  Branches      245      245           
=======================================
  Hits         1860     1860           
  Misses        191      191           
  Partials       51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[askpt]

I don't see any issues with this PR. Does this also sort the #440 or we should investigate it better?

[toddbaert]

Looks like this does solve #440 as well, at least partially? Should we mention that in the commit or break it out to another?

Looks good to me, let's just be careful to make sure to acknowledge that when we make this public we are adding more surface area to the SDK's API that we must not break; if there's any possible breaking changes we want to make to the serializer, lets make them now.

[askpt]

Looks like this does solve #440 as well, at least partially? Should we mention that in the commit or break it out to another?

For this I am happy to keep it in this PR and investigate it better in a separate effort. This PR adds the specific properties to announce this library is NativeAOT, which it seems it is by the test scenario in the pipeline. We can keep it in that PR and then make an official announcement or even add more testing around it.

Looks good to me, let's just be careful to make sure to acknowledge that when we make this public we are adding more surface area to the SDK's API that we must not break; if there's any possible breaking changes we want to make to the serializer, lets make them now.

I agree. I think @kinyoklion and @WeihanLi might have a better answer to it. I cannot see any possible breaking changes to this serialiser in the future (unless we add a new ValueType in the spec).

[WeihanLi]

@askpt @toddbaert thanks very much for the review, it does contribute to the #440 and agree with For this I am happy to keep it in this PR and investigate it better in a separate effort., this introduces initial AOT support for the JSON source generator verification, think we could investigate better separately.

For the json converter, think we may need to confirm on the convert type name and namespace since it's going to be public, and maybe also the document comment, to avoid future breaking changes.

Also cc @kylejuliandev for a review and input.