feat: added error state details into connection-error

[gautamsamal]

I am facing an issue where I am wondering if it's possible to distinguish the root cause of an ELOGIN error during the connection event. Although I know that in most cases SQL server doesn't send a state other than 1 (ref) but I hope that's configurable.

Assuming the same, does it makes sense to pass those information along with ConnectionError? The PR simply adds three properties (number, state, class) to the Error instance.

[IanChokS]

Thanks for raising this PR! We'll see what we can do about adding more error information regarding ELOGIN