Local Site Ids don't match Remote Site Ids

[lmatayoshi]

Though it doesn't produce negative effects, it can be misleading when cross-validating store and collector's data (When testing, for example)

Steps to reproduce:

1. Suppose there are initially 20 sites in the store, with ids going neatly from 1 to 20
2. Then, an admin deletes let's say, the last one and then creates a new one. So now ids are [1, 2... 19, 21]
3. When a new Collector joins and syncs it's local database, it will see the site ids ranging from [1, ..., 20] instead of realizing that the last Site actually has id = 21. This happens because the Sites list is using the ids of the local database instead of the remote ones

[lmatayoshi]

@mmuller, situation described above shouldn't happen anymore. Collectors should be able to see remote ids in the Sites list now, and no other screen should be displaying local sites ids