Improve connection API (where most user mistakes occur)

[alanseiden]

Reduce incidence of customer mistakes with a clearer API to connect to the toolkit.

One solution: allow array of options to be passed to getInstance() and constructor (either as param or with fluent interface). This would let us provide examples of a connection that does all necessary to define the connection. Solve several problems, including:
◦ users forgetting to add a separate 'stateless'/'InternalKey' setOptions statement, causing various nightmares
◦ inability to specify in code that we want to use HTTP transport (currently we have to specify in toolkit.ini with URL); we need to know the connection type and URL at connection time, not later. (Alan, clarify this issue)

[alanseiden]

We will address this issue cleanly in toolkit 2.0. See #87.
Meanwhile, let us help people by creating more examples that illustrate proper connection techniques. See #71.