Sql Database Projects - Improved Schema Compare save/open feature

[rmannjbs]

Is your feature request related to a problem? Please describe.

Via the Sql Database Project extension, the Schema Compare tools ability to save/open schema compares leaves much to be desired. Currently when you save it in the git repo you are working in it has hard coded absolute paths from the current users environment in it which makes them none portable between developers. Additionally they do not appear to save the options you select for excluding/including things.

We are no using this extension to manage all of our databases and have imported all of our databases with it into azure devops git repos, but currently there is no good way to deal with save/persisted schema compares which leads to errors with different developers not selecting the right things in the schema compare tool.

Describe the solution or feature you'd like
I would like to have a complete rethink of how the schema compare tool works inside of a database project. I still want to be able to manually open it and compare anything to anything sure. But I would like to have the ability to put them in a .vscode folder in a setting and have a file that works like tasks.json etc maybe called "schemaCompares.json" and be able to script them out. And then I would like to be able to launch them from the command pallete like tasks "Compare UAT Blah to Project Blah", and have them be portable by letting us use things like ${rootWorkspaceDir} etc like you can in vscode.

Also it's a must have feature to have all the selected compare objects/options persist in the schema compare file. And also to be able to not store user account info in the connection strings etc (all of our databases use mfa/azure auth) so I need a way to select the source/target server in the schema compare without having any user specific information in it. Ideally I woul-d be able to utilize launch profile inputs for this, so if a user name is needed I can make running that launch profile/task prompt for it.

Describe alternatives you've considered
Anything that makes saving schema compares shareable in the git repo without absolute paths in them.