Add table_name to AR geocoded and not_geocoded scopes

In queries involving two different geocoded models, there is a risk to hit a ``Mysql2::Error Column 'latitude' in where clause is ambiguous`` using ``geocoded`` scopes. 

This patch solves those situations.

PS: I could not run the suite test in my machine, let's trust travis.