The Action should be allowed to use Trusted Connections for SQL Server

When trying to run using "Trusted Connection" instead of SQL logins, we get an error message from the action.

At least for local SQL instances, we would expect that the Trusted Connection should be allowed and we are able to manage our databases using this action. Using SQL logins only, seems to be a step backwards.

> Error: Invalid connection string. Please ensure 'User' or 'User ID' is provided in the connection string.

Example Connection string: Data Source=< Server >\\< Instance >;Initial Catalog=< database >;Integrated Security=true;