Maintain alphabetical ordering across all connector registry files

[daviburg]

When new connector batches are added, entries are appended rather than sorted into their correct alphabetical positions. This affects:

1. ConnectorNames.cs — public const string entries
2. ManagedConnectors.cs — AvailableConnectors array and usage comment block
3. ConnectorServiceCollectionExtensions.cs — Add*Client DI methods, using directives
4. ConnectorServiceCollectionExtensionsTests.cs — registration chain and assertion block
5. .github/skills/connection-setup/SKILL.md — supported connector names list

The convention is alphabetical order by connector API name (e.g., azureautomation before azureblob). Batches 3 and 4 appended entries at the end rather than interleaving them.

Action: Re-sort all 5 files so all 60 connector entries are in strict alphabetical order. Consider adding a CI check or test that validates ordering.

Deferred from PR #134 Copilot review.