[Feature Request]: Allow bacpac export to pass additional flags

### Feature Description

Sometimes it might be necessary to pass additional flags to bacpac export (For example VerifyExtraction=False).
Currently, the feature that is under public preview, doesn't allow us to pass any additional arguments to SqlPackage. It will be nice to have this supported please.

### Problem and Motivation

There are instances with Database views spanning across multiple databases on the same server. Although this is anti pattern, we will have these cases for sure. In this case, we would like to pass VerifyExtract = False.
There could be other cases too.

### Related Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [ ] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [x] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [ ] Other (please describe below)

### If you selected "Other", please describe the area

_No response_

### Confirmation

- [x] I have searched existing feature requests and couldn't find a match
- [ ] I want to help implement this feature

No file, test, or entry point is named. Begin by locating the DACPAC/BACPAC export/import path and its SqlPackage invocation, then determine how export options are assembled. Done means callers can supply additional SqlPackage flags, including VerifyExtraction=False, while existing exports continue to work.

Written by the indexing model from the issue text.