Sort provider pool members by priority then weight

[MasonXon]

Why

The pool member list did not reflect the backend's actual call order, so users could not see which member would be tried first without opening each member's config.

The backend (orderedMembers() in provider_pool_inference.go) tries members in priority ascending order (lower priority first), and load-splits within the same priority by weight ratio.

What changed

sortProviderPoolMembers orders members by:

1. priority ascending — matches the backend call order (lower is tried first)
2. weight descending within the same priority — purely visual; within a priority there is no call order (members are load-split by weight ratio), but listing higher-weight members first matches the intuition that they carry more traffic.

Applied at three points so the list stays ordered during editing:

• opening the edit dialog (openProviderPoolDialog)
• after saving a member's config (saveProviderPoolMemberConfigDialog)
• when adding a member (toggleProviderPoolSourceModel)

The saved pool list page (ProviderPoolsSection) also sorts and now shows priority/weight badges on each member card, so the order and routing are visible without opening the editor. The edit dialog member cards already show the same badges.

Notes

• Weight tiebreaker is visual only — within a priority, members are equal; weight just sets the traffic split ratio.
• Stable within the same (priority, weight) — preserves the user's relative order for ties.