[Bug Bash] The sources order in ‘Package Source Mappings’ tab is inconsistent with ‘Package Source’ tab when they were added separately

[ZheeYoong1125]

NuGet Product Used

Visual Studio Package Management UI

Product Version

NuGet Client 6.15.0.17

Worked before?

It is not a regression since the issue reproes on D17.13\36008.115 with implicit NuGet 6.13.2.1 and the feature is not supported on D16.11\35912.113 with implicit NuGet 5.11.6.4.

Impact

It bothers me. A fix would be nice

Notes:        

1. The repro rate is 100%.  

2. It also reproes on non-SDK style projects.

3. It doesn't repro when all source mappings are added at the same time.

Repro Steps & Context

1. Create a C# Console App (.NET 9.0) project in VS and open the PM UI or PMC window.

2. Click the settings button (gear button) on PM UI or PMC window.

3.  Click the NuGet Package Manager->Package Source Mapping in the opened “Options” window.

4. Ensure that there are at least three package sources listed.

5. Click the “Add” button in the “Add New Package Source Mapping” dialog, type the package pattern “a” in the “Package pattern:” textbox, select source in order “1”and “3” and then click “Add” button.

6. Add another new package source mapping with the same name “a”, select source in order 2, and click “Add” button.

7. Click “OK” button and reopen “Package Source Mapping” in option windows.

Expected:   

The order of package sources in the “Package Source Mapping” tab should match the order shown in the “Package Sources” tab.

Actual:    

The order of package sources in the “Package Source Mapping” tab doesn’t match the order shown in the “Package Sources” tab as the record below.

Verbose Logs

[nkolev92]

The package sources showing them by the priority of the nuget.configs (sources themselves don't have priority), while the 2nd one is alphabetical.

I'd say the alphabetic one is good and I wouldn't want to change it.
So, if anything, I'd maybe consider changing the package sources, but the impact of it is low.
Quick check I didn't find any issues around this.