Fix staticcheck SA5011 false positives in function_lifecycle_test.go

Add explicit return statements after t.Fatal() calls to make it clear
to staticcheck that execution terminates, preventing false positive
nil pointer dereference warnings.

This resolves intermittent lint failures in the merge queue where
staticcheck SA5011 would complain about potential nil dereferences
even though t.Fatal() terminates execution.

Author: creydr

api/v1alpha1/function_lifecycle_test.go

@@ -95,6 +95,7 @@ func TestCalculateReadyCondition(t *testing.T) {
 			readyCondition := meta.FindStatusCondition(f.Status.Conditions, TypeReady)
 			if readyCondition == nil {
 				t.Fatal("Ready condition not found")
+				return
 			}
 
 			if readyCondition.Status != tt.expectedStatus {
@@ -149,6 +150,7 @@ func TestInitializeConditions(t *testing.T) {
 	readyCond := meta.FindStatusCondition(f.Status.Conditions, TypeReady)
 	if readyCond == nil {
 		t.Fatal("Ready condition not found")
+		return
 	}
 	if readyCond.Status != metav1.ConditionUnknown {
 		t.Errorf("Ready condition: expected status Unknown, got %v", readyCond.Status)