Fix in logical comparisons of undefined argument values against `null` for setting default argument values in few methods in CCNode, CCSprite and CCSpriteBatchNode

Fixed comparison against few function arguments from using strict equality === against null to weak equality == as undefined values wouldn't cause the default values to be assigned as expected which could cause memory leaks as cleanup wouldnt get triggered on node removal neither for removed node nor for the child nodes when using the removeFromParent, removeChild and removeAllChildren if somebody didn't specify explicitly `true` while removing which should be default.

Also CCSprite default zOrdering and tag wouldn't be set properly for the same reason.

(And thanks guys for awesome work!)