fix: sort no longer panics on a value tagged as a number that is not one

sortableNodeArray.compare called panic(err) when parseInt64 or ParseFloat
failed, so a scalar tagged !!int or !!float whose value is not a number
crashed yq with a Go stack trace. An explicit tag in the input document is
enough to trigger it, no unusual expression needed.

Log a warning and compare the raw strings instead, matching the timestamp
branch a few lines above in the same function and the plain string fallback
the function already ends with. Values that do parse still compare
numerically.

pkg/yqlib/operator_sort_test.go

@@ -180,6 +180,42 @@ var sortByOperatorScenarios = []expressionScenario{
 			"D0, P[], (!!seq)::[-5000000000000000000, 5000000000000000000]\n",
 		},
 	},
+	{
+		skipDoc:     true,
+		description: "Sort values tagged as ints that are not ints",
+		document:    "[!!int b, !!int a]",
+		expression:  `sort`,
+		expected: []string{
+			"D0, P[], (!!seq)::[!!int a, !!int b]\n",
+		},
+	},
+	{
+		skipDoc:     true,
+		description: "Sort values tagged as floats that are not numbers",
+		document:    "[!!float b, !!float a]",
+		expression:  `sort`,
+		expected: []string{
+			"D0, P[], (!!seq)::[!!float a, !!float b]\n",
+		},
+	},
+	{
+		skipDoc:     true,
+		description: "Sort a number against a value tagged as a number that is not one",
+		document:    "[!!int zz, !!float 1.5]",
+		expression:  `sort`,
+		expected: []string{
+			"D0, P[], (!!seq)::[!!float 1.5, !!int zz]\n",
+		},
+	},
+	{
+		skipDoc:     true,
+		description: "Sort a map by a value tagged as an int that is not one",
+		document:    "{a: !!int notanumber, b: !!int 3}",
+		expression:  `to_entries | sort_by(.value) | from_entries`,
+		expected: []string{
+			"D0, P[], (!!map)::b: !!int 3\na: !!int notanumber\n",
+		},
+	},
 }
 
 func TestSortByOperatorScenarios(t *testing.T) {