Make a Feed query construction less clever/sneaky for new qsprintf() semantics
I can't reproduce the string-vs-int MySQL key issue on any system I have access to, so just simplify this and format as ('1', '2', '3') instead.
The issue this is working around is that MySQL would (I think?) sometimes appear to do something goofy and miss the key if you formatted the query with strings. I never really nailed this down and could have either been mistaken about it or it could be fixed in all modern versions of MySQL. Until we have better evidence to the contrary, assume MySQL is smart enough to handle this sensibly now.
Test Plan: Ran daemons with Feed publish workers, no longer received query warnings.
Reviewed By: amckinley
Differential Revision: https://secure.phabricator.com/D19837