Improve transport logic (support batch requests)

[jharding]

Piggyback off of pending requests intelligently. Previously the following code would result in 2 separate requests being made to https://twitter.com?q=query:

var transport1 = new Transport({ 
      url: 'https://twitter.com?q=%QUERY' 
    }),
    transport2 = new Transport({ 
      url: 'https://twitter.com?q=%QUERY'
    });

transport1.get('query');
transport2.get('query');

Now, before a transport makes a request to a url, it checks to see if there's already a pending request to that url and if there is, it'll rely on the response from that pending request.

The main benefit of this is that it's now possible to do batch requests i.e.

$('.typeahead').typeahead([
  {
    name: 'colors',
    remote: {
      url: 'http://everything.com?q=%QUERY',
      filter: function(resp) { return resp.colors; }
    }
  },
  {
    name: 'numbers',
    remote: {
      url: 'http://everything.com?q=%QUERY',
      filter: function(resp) { return resp.numbers; }
    }
  }
]);

This pull request also fixes a bug mentioned in #151.

[jharding]

@timtrueman can you give this a once over when you get a chance? No rush.

[timtrueman]

The word "batch" confused me into thinking this would batch requests into a single request but this code looks great; it's just more of a shared request cache than a batched request model.

Ship it.