Creating a connection to an Azure database may fail when other databases are on the same server

If an Azure SQL Server has a database which is not a Jiwa database (does not have the user JiwaLogin), then the connection wizard will not allow you to select any database on the server - the following error occurs:

Unable to connect to server '%s' as user 'jiwalogin', password 'JiwaApplicationLogin123'.

The error is caused by the enumeration of the databases list in the SQL SMO objects.  Even if a database does not have the JiwaLogin user, we should not prevent the user from selecting a database which does have the login.

Steps to reproduce:

1. Create a new SQL database in the Jiwa Financials SQL Subscription
2. Open Jiwa and from the Login form choose the connections... button
3. In the connection wizard, enter the name of the SQL Server
4. On the database drop-down combobox, press the drop-down arrow and the error occurs.

The source of the issue is in the JiwaFinancials.Jiwa.JiwaApplication.ConnectionManager.Connection class - there is a property, DatabaseList which does the following:

For Each Database As Database In Server.Databases

And this line is causing the exception.

A work-around is to simply add a user to the other databases on the SQL Server named 'JiwaLogin' which is linked to the SQL Login 'JiwaLogin', or manually creating the connection by editing the JiwaConnections.xml file in the %appdata%\Jiwa Financials folder.