Fix couch_replicator_mangaer changes feed upgrades

The changes feed readers were unnecessarily holding onto anonymous
functions. This makes it so they dont.

BugzId: 27666
Don't die when a known replicator related pid dies

The couch_replicator_manager would die when any replication related pid
exited. Instead of that we don't. This means we don't cancel and restart
all known replications that happen to be running on the node due to an
error starting replications for a given database or document.

BugzId: 27666