fix: verb call order (#2940)

we can't sort this way because the generated resource providers need to
match the param ordering to ensure they pass the correct resources in
place. will have to think of another solution to stable sort here

go-runtime/schema/schema_test.go

@@ -273,7 +273,7 @@ func TestExtractModuleSchemaTwo(t *testing.T) {
 				+calls two.two
 
 			export verb callsTwoAndThree(two.Payload<String>) two.Payload<String>
-				+calls two.three, two.two
+				+calls two.two, two.three
 
 			export verb ingress(builtin.HttpRequest<two.PostRequest, Unit, Unit>) builtin.HttpResponse<two.PostResponse, String>
 				+ingress http POST /users

go-runtime/schema/verb/analyzer.go

@@ -3,7 +3,6 @@ package verb
 import (
 	"go/ast"
 	"go/types"
-	"slices"
 	"strings"
 	"unicode"
 
@@ -94,7 +93,7 @@ func Extract(pass *analysis.Pass, node *ast.FuncDecl, obj types.Object) optional
 	}
 	verb.Request = reqV
 	verb.Response = resV
-	sortMetadata(verb)
+
 	return optional.Some(verb)
 }
 
@@ -172,16 +171,3 @@ func getResourceRef(paramObj types.Object, pass *analysis.Pass, param *ast.Field
 	}
 	return dbRef
 }
-
-func sortMetadata(verb *schema.Verb) {
-	for _, md := range verb.Metadata {
-		if calls, ok := md.(*schema.MetadataCalls); ok {
-			slices.SortFunc(calls.Calls, func(i, j *schema.Ref) int {
-				if i.Module != j.Module {
-					return strings.Compare(i.Module, j.Module)
-				}
-				return strings.Compare(i.Name, j.Name)
-			})
-		}
-	}
-}