Add backtrace info to "surprise method call" logging

We are currently logging (just rails log) whenever something calls `Proposal#update_votes_count`, because Liquidvoting doesn't use it, and it will corrupt our vote count.

The log line is nice, but doesn't help us know where it comes from; adding a backtrace in the log would do that.

This issue might be superceded by some Honeycomb events work.

Start by locating the existing log statement for Proposal#update_votes_count and review how the unexpected call is currently recorded. Add the requested backtrace information to that log and verify that a surprising call produces useful origin details; first confirm the work has not been superseded by Honeycomb events.

Written by the indexing model from the issue text.