Lower throttle for Cirrus template update jobs

The first throttle level wasn't enough to start building up a backlog.  Lets
half it and see if that gets us a backlog.  The goal here is to get a
constant backlog so we're seeing something close to even distribution of
the jobs across time.  It'd be a bonus if we can get job deduplication out
of it but with only a few minutes of backlog that is unlikely.

Change-Id: If678aa012c64867ccfcdb31e70830a87bafa423d
Separate high traffic Elasticsearch shards

This keeps Elasticsearch from putting enwiki content shards next to each other
and frwiki content shards next to each other, etc.  It does not keep enwiki
shards from frwiki shards.  Oh well, thats still worth something.

DEPLOYMENT: This has already been applied directly to the index.
DEPLOYMENT: This won't do anything (and index rebuilds will remove the
settings dynamically applied to the index) unless
I83a9a4b23c3edb2cd177dfccdd7e650598ee2a22 is already deployed.

Change-Id: I15b26dfdc7f3fb9f37e0ec24440291ae991aaf20
Merge "Lower throttle for Cirrus template update jobs"
Merge "Separate high traffic Elasticsearch shards"