fic(ifc): Fix for element quantities that contain nan values

[JR-Morgan]

We got some alerts of a flood of 400 errors triggered by IFC uploads.

I believe this is caused by NaN values being sent to the server.
js and python disagree with how to serialize NaN values, so the server was handling the post requests to /objects/:streamId as invalid json.

In this PR, for IFC values that we know may be NaN, I'm mapping them to None values.
This follows the js standard of mapping to null value
The python standard is to serialize them as a NaN keyword value.

I've also see other serializers write a "NaN" value instead... but felt that none is easier to deal with than mixing types.

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #458   +/-   ##
=======================================
  Coverage   90.61%   90.61%           
=======================================
  Files         138      138           
  Lines        6373     6373           
=======================================
  Hits         5775     5775           
  Misses        598      598           

☔ 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.