Calling isc_nm_read_stop() doesn't stop readcbs already in progress

When isc_nm_read_stop() is called, it doesn't stop the read callbacks already scheduled on the worker->loop.

This breaks the "promise" as the parent may have already destroyed the object (etc...).

This needs to be fixed before 9.20...