Add support for more file types (beyond .bak) in the --using flag (sqlcmd create)

The initial PR for the --using flag (in sqlcmd create mssql) enables the scenario:

sqlcmd create mssql --using https://aka.ms//AdventureWorksLT.bak

i.e. create a new local T/SQL endpoint with the AdventureWorks database downloaded and restored from a URL

--using should support all normal source type that contain databases, e.g. .bacpac files, and .mdf/.ldf (in archive files, like .zip/.7z etc.).

--using should just do the right thing depending on what it finds, e.g. do a restore of a .bak file / do an attach of a .mdf/.ldf file etc.

--using should also support more protcols than just http(s)://, it should definitely support file:\, including c:\ etc.

(the idea here is the end user shouldn't need to know the mechanism required to get the database attached to the engine, they just provide the URL to the file, and sqlcmd does the rest).

Start by tracing the existing sqlcmd create mssql --using flow and how it handles the .bak URL. Inventory the requested source types and protocols, then define completion as choosing the appropriate restore or attach behavior for each supported input, including local file:\ paths and archive files.