proc: Removed setChanRecvBreakpoints
proc: Removed setChanRecvBreakpoints

This function was broken for a very long time until the changes in this
PR fixed it. However I do not think it is desirable to be catapulted
into some other goroutine by 'next' just because that other goroutine
happened to receive a message on a channel.

This feature should be implemented by a new command, not next.

dlsniper/delve,alexbrainman/delve,derekparker/delve,dlsniper/delve,go-delve/delve,dr2chase/delve,derekparker/delve,alexbrainman/delve,go-delve/delve,go-delve/delve,dr2chase/delve,ggndnn/delve,dr2chase/delve,ggndnn/delve,ggndnn/delve,aarzilli/delve,derekparker/delve,aarzilli/delve,go-delve/delve,alexbrainman/delve,go-delve/delve,aarzilli/delve,aarzilli/delve,dlsniper/delve