Many numbers have a possible 'null' value in the websocket api

[daboross]

It's currently assumed that numbers such as nextRegenerationTime in Source, or resource numbers in terminals, are either non-existant, or 0. This simply isn't true: both of these can also be null.