Patched HTTPS Issue with Twitter and Added some checking around issues with Twitter and Rate Limiting

Currently the Net::Twitter::Lite::WithAPIv1_1 module defaults to using non-https for connecting to the API. As of Jan 14th, Twitter now requires HTTPS for all transactions.  This fixes that issue till the module is updated accordingly. 

The second this is that not all 403 messages is about rate limiting.  I added the ability to see that twitter error code and message during a 403. If the twitter Error code is a 187, it will provide a different error saying that it is a duplicate message and not a rate limiting issue. 

We can continue to update that section with the appropriate error code as we find them. Then we can begin to act upon them accordingly.