Simplify the "is integer" checks in `CFFCompiler.encodeNumber`
Simplify the "is integer" checks in `CFFCompiler.encodeNumber`

The `isNaN` check is obviously redundant, since `NaN` is the only value that isn't equal to itself; see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NaN#Examples

The `parseFloat`/`parseInt` comparison would make sense if the `value` ever contains a String, which however is never actually the case. Besides looking through the code, I've also run the entire test-suite locally with `assert(typeof value === "number", "encodeNumber");` added at the top of the method and there were no failures.

Hence we can simplify the "is integer" check a bit in the `CFFCompiler.encodeNumber` method.

Shoobx/pdf.js,showpad/mozilla-pdf.js,caremerge/pdf.js,mozilla/pdf.js,Snuffleupagus/pdf.js,Shoobx/pdf.js,mozilla/pdf.js,Shoobx/pdf.js,timvandermeij/pdf.js,macroplant/pdf.js,timvandermeij/pdf.js,macroplant/pdf.js,timvandermeij/pdf.js,caremerge/pdf.js,mozilla/pdf.js,nawawi/pdf.js,xavier114fch/pdf.js,showpad/mozilla-pdf.js,nawawi/pdf.js,Snuffleupagus/pdf.js,showpad/mozilla-pdf.js,macroplant/pdf.js,Snuffleupagus/pdf.js,xavier114fch/pdf.js,nawawi/pdf.js