update naturalsort sorting with slice

[thaJeztah]

• stacked on modernize code with slices and maps packages #7268
• stacked on vendor: github.com/fvbommel/sortorder v1.2.0 #7271

vendor: github.com/fvbommel/sortorder v1.2.0

full diff: fvbommel/sortorder@v1.1.0...v1.2.0

- Human readable description for the release notes

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

❌ Patch coverage is 88.23529% with 4 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
cli/cobra.go	0.00%	2 Missing ⚠️
cli/command/stack/services.go	0.00%	1 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[docker-agent]

⚠️ Review incomplete

chunk 1: Drafter did not complete
chunk 2: Drafter did not complete
chunk 3: Drafter did not complete

All three drafter delegations failed with a sub-agent schema validation error (output_config.format.schema: Unsupported regex feature). The automated hypothesis-generation pipeline could not run.

Manual inspection summary (orchestrator-level): The diff was reviewed directly. This PR is a clean mechanical migration from sort.Slice/sort.Sort to slices.SortFunc/slices.SortStableFunc in tandem with vendoring github.com/fvbommel/sortorder v1.2.0 (which adds NaturalCompare for three-way comparison). All comparator semantics were verified to be preserved correctly:

• sort.Slice → slices.SortFunc conversions: comparator directions correct throughout.
• sort.SliceStable / sort.Stable → slices.SortStableFunc: stability preserved.
• slices.SortedFunc(maps.Values(emptyMap), ...) returns nil in Go 1.24, so the updateUlimits "remove all" test expectation (nil) remains satisfied.
• cmp.Or / cmp.Compare port-sort replacements match the original field ordering.
• formatAdminRole key-ID sort now creates a copy instead of mutating the receiver — a bug fix.
• toStringList %s → %v format change is safer for non-string any values.
• filepath.IsLocal path-escape check in cli/config/config.go is more robust than the old strings.HasPrefix approach.

No bugs were identified in the manual pass. However, since the automated pipeline did not complete, this review cannot be treated as a full automated review.

Findings so far: ⚠️ INCOMPLETE