SAS token expiry time values needs an upper boundry

[timtay-microsoft]

Setting a SAS token expiry time of 40 years and connecting over AMQP leads to some kind of integer overflow that causes SAS tokens to be sent to the service rapidly. Because of that, we should probably add some SDK-side check that prevents any values that would cause this kind of overflow.

Still TBD what happens over MQTT or HTTP

[timtay-microsoft]

Version 2.3.1 has been released with this fix, so I'll close this thread