Allow the last callback called to add a callback

This fixes a bug in the finished and response callbacks where if the last/only callback adds another callback, the newly added callback won't be called afterwards.

This is because when it tries to add the callback, it is added to a new list instance because the callbacks list is empty at that time; the check for whether the callbacks list was created didn't previously distinguish between an empty list and not a list.  However, if it is not the last callback in the list, the callbacks list will not be empty and the new callback will be added to the same list and the newly added callback *will* be called.

Because the code as written appears to be trying to support callbacks adding callbacks, this push request modifies the code so that a callback may add another callback whether it is the last one or not.

An alternative approach would be to modify the code so that callbacks cannot add new callbacks, which also would be reasonable.  But I think it's a bug that the behavior depends currently on whether you are in the last/only callback when you try to add another one.
Add a test case for a response callback adding a response callback when it is the only callback.
Use None for the default value of the callbacks list.
Use a deque for the request finished / response callbacks.
Fix a few tests that assume response_callbacks was a list
Merge pull request #1373 from dobesv/patch-5

Allow the last callback called to add a callback