Fix Crystal 1.14.0 compilation error undefined constant ConnectionBuilder

[lachlan]

Compiling the TDS driver with Crystal v1.14.0 results in the following error:

C:\crystal-tds>crystal spec
Showing last frame. Use --error-trace for full trace.

In src\tds\driver.cr:13:5

 13 | ConnectionBuilder.new(connection_options(params), TDS::Connection::Options.from_uri(uri))
      ^----------------
Error: undefined constant ConnectionBuilder

The ConnectionBuilder class had inadvertently been declared with an extra TDS level in its namespace by mistake:

TDS::Driver::TDS::ConnectionBuilder

Then it was later referred to using TDS::ConnectionBuilder which somehow worked on previous versions of the compiler.

This fix removes the extra TDS level from the ConnectionBuilder namespace, as this was a typo, and changes references to use the fully-qualified name TDS::Driver::ConnectionBuilder.

Also fixes the compilation warning that sleep(Number) is deprecated by replacing the calls with sleep(Time::Span) instead.

[lachlan]

I did some further research, and I believe it was this pull request in Crystal 1.13.0 that changed the compiler behaviour that resulted in the compilation error undefined constant ConnectionBuilder: crystal-lang/crystal#11208.

Given the original (erroneous) declaration of ConnectionBuilder:

class TDS::Driver
    class TDS::ConnectionBuilder
    end
 end

Prior to 1.13.0 the compiler had a bug that resulted in that declaration creating the types ::TDS::Driver and ::TDS::ConnectionBuilder, so later references to the unadorned ConnectionBuilder within Driver resolved without issue as they were in the same module / namespace.

The above pull request in 1.13.0 fixes this compiler bug, so the above declaration now creates the types ::TDS::Driver and ::TDS::Driver::TDS::ConnectionBuilder, so later references to the unadorned ConnectionBuilder within Driver no longer resolves as the types are no longer in the same module / namespace.

This fix puts the ConnectionBuilder type within the ::TDS::Driver namespace, and also uses a fully-qualified reference to ensure there are no type name clashes when other DB drivers are loaded in the same process with the TDS driver.

[wonderix]

Thank you for your PR.