This PR addresses issue#532 regarding inconsistencies in the return values for various frequency response functions. The changes fixes a number of previous inconsistencies, where state space and transfer function representations could return different values and evaluating the frequency response at the "origin" gave different values depending on whether you evaluated at 0 or 0j.

The changes here only affect results when evaluating the system at a pole of the system.

In this PR:

• State space systems and transfer functions return the same values when evaluated at poles (including poles at the origin):
  • Evaluation at 0 with pole at the origin: returns (inf + nanj)
  • Evaluation at non-origin pole with nonzero numerator: returns (inf + infj)
  • Evaluation at pole with cancellation by a zero: returns (nan + nanj)
• State space systems and transfer functions interpret argument as a complex number, so that G(0) and G(0j) return the same value.
• Computing the DC gain is (exactly) the same as evaluating at 0

A few other small changes:

• Added awarn_infinity flag to all functions used to evaluate frequency response. By default this is set toTrue, in which case you get a divide by zero warning or singular matrix warning when evaluating at a pole. Setting it toFalse suppresses this warning. (Also,dcgain setswarn_infinity to False by default).
• Updated docstrings and unit tests