:TEST-NOT handling by functions

[Nikodemus Siivola]

  We should verify that our handling of :TEST-NOT and :TEST is consistent
  for all functions that accept them: that is, signal an error if both
  are specified.

  Similarly, a compile-time full warning for calls with both would be good.

  We might also consider a compile-time style warning for :TEST-NOT.

[Tobias C. Rittweiler (tcr)]

Attached is a file with tests for all functions taking :TEST and :TEST-NOT
(caveat: the list of such functions was generated programmatically.)

I tried to fix it for the sequence functions but this would mean refactoring
of DEFINE-SEQUENCE-TRAVERSER, and I better leave that to the experts.

Or perhaps you can depict shortly how you'd like the interface to be.