[Feature Request]: SQL Database Projects do not support targeting Microsoft Fabric SQL Analytics Endpoint

### Feature Description

The VS Code mssql extension’s SQL Database Projects functionality does not currently support projects that target Microsoft Fabric SQL Analytics Endpoint. This prevents teams from using SQL projects to build, validate, and deploy database objects as part of a standard CI/CD / DevOps process.

### Problem and Motivation

There is no supported target platform (DSP / project target) corresponding to Fabric SQL analytics endpoint.

Attempts to use existing targets (Azure SQL DB, Synapse, etc.) either:

fail validation/build due to unsupported/unknown features, or

publish with incorrect assumptions about supported objects.

This blocks deployment automation and forces manual changes in Fabric.

### 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
- [x] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [x] DACPAC/BACPAC export/import
- [x] 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

The issue does not name files or tests. Start by tracing the SQL Database Projects target-platform handling and the Schema Compare and DACPAC/BACPAC integration, comparing the existing Azure SQL DB and Synapse targets. Done means Fabric SQL Analytics Endpoint projects can build, validate, compare schemas, and deploy without incorrect target assumptions.

Written by the indexing model from the issue text.