Managed Instance restores

[Stuart-Moore]

Type of Change

• Bug fix (non-breaking change, fixes #)
• New feature (non-breaking change, adds functionality)
• Breaking change (effects multiple commands or functionality)
• Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
• Adding code coverage to existing functionality
• Pester test is included
• If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
• Nunit test is included
• Documentation
• Build system

Purpose

Implements #5297 and prevents non compatible parameters being pushed through to a managed instance

In draft as there's be some other bits to come as people spot issues or come up with other use cases. But only expecting it to be around a day or so.

Approach

Check the DatabaseEngineEdition property of the restore server. If it's SqlManagedInstance then check parameters and stop if anything that MI won't touch aren't being used.

If withreplace is needed and specified then do a drop/restore as traditional WithReplace isn't supported

Commands to test

$op = Get-DbaBackupHistory -SqlInstance localhost -database mitest | Restore-DbaDatabase -SqlCredential $cred -SqlInstance dbatoolsmi.cus19c972e4513d6.database.windows.net -TrustDbBackupHistory -DatabaseName tes3t  -verbose

[Stuart-Moore]

Merging as I need it for the Copy-DbaDatabase work