spec: Don't expect getOldFactionWar in TyrantHistory init
spec: Do not expect getOldFactionWars in news check

We switched to using getFactionWarInfo long ago, so we expect NOT to
receive a getOldFactionWars. We should check this
spec: Allow File.exist? on /dev/null/1 in !faction

libtyrant is now using exist? instead of deprecated exists?
spec: Expect another getFactionRivals in each !targets test
rspec: Use rspec expectations on FakeConnection#respond

This means we can do stricter checking for the passed parameters and
return different things based on the parameters.

!targets tests now no longer return duplicates
spec: Always explicitly specify params to API calls

Previously, a nil param indicates any params were accepted. It is better
to be stricter in our checks to make sure we are actually sending the
right params. Params are always explicitly specified now, even if the
params are explicitly empty.
Merge branch 'spec-params'

* spec-params:
  spec: Always explicitly specify params to API calls
  rspec: Use rspec expectations on FakeConnection#respond
  spec: Expect another getFactionRivals in each !targets test
  spec: Allow File.exist? on /dev/null/1 in !faction
  spec: Do not expect getOldFactionWars in news check
  spec: Don't expect getOldFactionWar in TyrantHistory init