feat: sorting for the NetworkMock operation list

[MaxMichel2]

Summary

Follow-up from #114, which added a bottom-bar search field plus version and HTTP method filters to NetworkMockScreen. Sorting was explicitly scoped out of that issue: the list currently renders in the OpenAPI spec's own paths declaration order, which mirrors the spec author's own grouping and is arguably already a sensible default — adding a sort control on top of an already three-dimension filter bar (version, method, search) needs its own design pass rather than being folded in.

Scope, when picked up

• Candidate sort keys: alphabetical by path, by method (canonical HttpMethod.DefaultMethods order, same ordering already used for the method filter chips), by tag (if feat: parse and expose OpenAPI operation tags #116 lands first).
• Needs a UI affordance that doesn't further crowd the bottom bar — an overflow menu or a segmented control in the top app bar area are the two obvious candidates; evaluate against the existing bottom-bar layout before committing.
• Sort state would presumably live alongside searchQuery/selectedVersions/selectedMethods in NetworkMockScreen.kt's ContentState — client-side only, no ViewModel round-trip, consistent with how the other filters are handled.

Open question

Where the sort control lives in the UI — resolve at design time, not here.