etherpad.js reverses order of etherpad hosts

This is resulting in the inability to publish in cluster. We probably shouldn't try and re-order, as the order of hosts is cross-dependent on the order in Nginx (for the hash index lookup).

It should simply be a requirement that the array ordering is consistent in the index-based Nginx config and config.js