SQLPackage Extract generating unusable .sql with /p:ExtractTarget=File

Nobody has claimed this yet.

- SqlPackage or DacFx Version:
- .NET Framework (Windows-only) or .NET Core:
- Environment (local platform and source/target platforms):

**Steps to Reproduce:**

1. Run SqlPackage extract against a database containing multiple schemas, user-defined types, and objects with dependencies.
Command used: `sqlpackage /Action:Extract /SourceServerName:shared-server-1.database.windows.net /SourceDatabaseName:adv-works-7e9sf /SourceUser:"username" /SourcePassword:"Password" /TargetFile:"test.sql" /p:ExtractAllTableData=False /p:ExtractTarget=File /p:VerifyExtraction=true`
2. Inspect the generated test.sql file.
3. Attempt to execute the generated test.sql file against a new or empty database.

**Expected behavior:**

The test.sql file generated by the extract operation should be topologically sorted. This means all dependency objects should be created before the objects that depend on them. For instance, CREATE SCHEMA and CREATE TYPE statements should appear at the beginning of the file, before any CREATE TABLE statements that use them. The resulting script should be executable and should successfully recreate the database schema.

**Actual behavior:**
The order of SQL commands in the file generated by `SqlPackage /Action:Extract /p:ExtractTarget=File` is not topologically sorted.

An investigation of the generated test.sql file shows that critical dependency statements are located at the end of the file instead of the beginning. Specifically:

`CREATE SCHEMA [rubrik]` and `CREATE SCHEMA [SalesLT]` statements appear at the end of the script.
User-defined types like `[dbo].[NameStyle]` and `[dbo].[Name]` are created after tables that depend on them.
This incorrect ordering makes the script unusable and causes numerous errors upon execution, such as:

The error while trying to use the `.sql` file
The `.sql` generated

_Made it .txt as github wasn't allowing to attach .sql file_

[test.txt](https://github.com/user-attachments/files/20824876/test.txt)

**Did this occur in prior versions? If not - which version(s) did it work in?**
Yes it did
(DacFx/SqlPackage/SSMS/Azure Data Studio)

Start by reproducing the issue with the supplied SqlPackage Extract command and inspect the generated test.sql and attached test.txt. Verify whether schemas and user-defined types are emitted after dependent tables; done means the extracted script is topologically ordered and executes successfully against a new database.

Written by the indexing model from the issue text.