[Bug fix] Changes feed duplicating results

[mharrigan26]

Overview

• Update the logic used for populating the changes feed. The query now uses the since parameter when loading new changes for the current database. This stops previously loaded changes from being passed as new ones and being duplicated.
• The internal state will reset when switched to a new database, so changes aren't carried over. A hard reset was only happening with a manual reload, so changes for multiple databases were appearing in one feed.
• Change the message on the changes feed to Limiting results to 100 changes instead of Limiting results to latest 100 changes since the order cannot be guaranteed.

Testing recommendations

Click on changes for any database. Click away within the document side panel (e.g. permissions) then switch back to changes. The feed should stay consistent and no longer be inundated with duplicated changes. Make a new document and switch back to changes, this should be the only change reflected in the feed. Then create a new database with no documents. That changes feed should be empty. This is new behavior that fixes a bug in the changes feed.

GitHub issue number

Related Pull Requests

Checklist

• [ ] Code is written and works correctly;
• [ ] Changes are covered by tests;
• [ ] Documentation reflects the changes;
• [ ] Update rebar.config.script with the correct tag once a new Fauxton release is made