fix: match _try_parse("NaN") behaviour with json.parse("NaN")

[kevinguo455]

Linked issue(s)

What change does this PR introduce and why?

Before #600, json.parse was previously used where _try_parse is now used. json.parse("NaN") returns a float nan value, while _try_parse("NaN") currently returns a string "NaN". This PR changes the behaviour of _try_parse("NaN") to match that of json.parse("NaN"), i.e. _try_parse("NaN") is changed to return a float nan.

This change will resolve this shipyard test failure: https://app.circleci.com/pipelines/github/kolenaIO/shipyard/8026/workflows/eb6a354a-43af-4210-ad28-0d03a7e06032/jobs/149222?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-checks-link&utm_content=summary

Please check if the PR fulfills these requirements

• Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
• Relevant tests for the changes have been added
• Relevant docs have been added / updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.49%. Comparing base (2cbe05d) to head (f230eeb).

Additional details and impacted files

@@           Coverage Diff           @@
##            trunk     #626   +/-   ##
=======================================
  Coverage   94.49%   94.49%           
=======================================
  Files          86       86           
  Lines        5395     5397    +2     
  Branches      791      792    +1     
=======================================
+ Hits         5098     5100    +2     
  Misses        220      220           
  Partials       77       77           

Flag	Coverage Δ
integration	76.24% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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