Invoke-DbaQuery, re-wire connection with integrated as another user

[niphlod]

Type of Change

• Bug fix (non-breaking change, fixes connection or connection info from Connect-DbaInstance not reused by Invoke-DbaQuery using Windows credential as SqlCredential #9579, fixes The SQL server object created by this cmdlet uses the wrong credentials #9459 )
• New feature (non-breaking change, adds functionality, fixes # )
• Breaking change (affects multiple commands or functionality, fixes # )
• Ran manual Pester test and has passed (Invoke-ManualPester)
• Adding code coverage to existing functionality
• Pester test is included
• If new file reference added for test, has is been added to github.com/dataplat/appveyor-lab ?
• Unit test is included
• Documentation
• Build system

Purpose

Tried to put it all in the new comments. Feel free to ping me on Slack for further details.
I'd like someone to try it in their own environment and see if it breaks things.

Small test

$cred = Get-Credential 'domain\anotheruser'
$server = Connect-DbaInstance -SqlInstance 'yourinstance' -Database dbatools -SqlCredential $cred
Invoke-DbaQuery -SqlInstance $server -Query 'select suser_sname()'
$server.Query('select suser_sname()')

Approach

Path of least resistance, should kick in and recreate the connection only if needed, if not, back to pooling that helps with performances.

[potatoqualitee]

I remember adding that code for a reason. @andreasjordan do you? I believe it's for secondary domains. Like if you on AD and try to connect to HOME

[andreasjordan]

I remember adding that code for a reason. @andreasjordan do you? I believe it's for secondary domains. Like if you on AD and try to connect to HOME

Sorry, I don't remember the reason. I don't have a lab to test the change and I don't have time to build one right now.

[potatoqualitee]

Thank you, @niphlod ! Thanks for the response, @andreasjordan.

I have merged it but will need to create a release when I'm at home with my lil hardware tool.