Don't restart memcached on a config change

I don't think it's the right thing to do to restart memcached via puppet on a config change. During standard maintenance it'd be nice to have the option to change the config w/o having brief downtime.

For instance we're going to reduce the RAM allocated for caching a bit and introduce a new cluster. That will involve one brief downtime while memcached restarts, and then a "flush" as the new cluster is brought into play. It'd be nicer not to have that restart.

Technically we could get around that config restart by using a branch env on the new servers. Then when the branch is merged into master after the switch to new servers there'd be no restart since the config file hadn't changed. But if we did that, what's the point of the auto-restart? To make things easier in qa which has fewer servers anyway?