HPCC-12486 Optimize binding module functions

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Somebody could... but equally they could pass in an invalid or recently freed pointer, and we would still crash. For internal functions the level of parameter checking that is appropriate is not necessarily the same as for external ones. Where should you draw the line? My view is we should put in assert(NULL) or assertex(NULL) where there is a non-trivial likelihood of getting passed a NULL. Other times it's ok to simply state (or imply) that it's part of the interface that a non-null pointer is expected. Checks are not free, and are not automatically always worth the cost.