feat: restrict-plus-operands: improve diagnostic (#725)

NOTE: There is an issue with help messages not showing up in snapshots, I will fix this in the following PR.

This rule's error message is packed with both type information and help information (what types are allowed). I've moved the resolved type info to be labeled ranges, and moved the message about what types are allowed to the help message. This should keep the information a little bit more structured and not crowd the main error message as much.

Author: camchenry

e2e/__snapshots__/snapshot.test.ts.snap

@@ -3298,8 +3298,24 @@ exports[`TSGoLint E2E Snapshot Tests > should generate consistent diagnostics sn
   {
     "file_path": "fixtures/basic/rules/restrict-plus-operands/index.ts",
     "kind": 0,
+    "labeled_ranges": [
+      {
+        "label": "Type: bigint",
+        "range": {
+          "end": 12,
+          "pos": 10,
+        },
+      },
+      {
+        "label": "Type: number",
+        "range": {
+          "end": 16,
+          "pos": 15,
+        },
+      },
+    ],
     "message": {
-      "description": "Numeric '+' operations must either be both bigints or both numbers. Got \`bigint\` + \`number\`.",
+      "description": "Numeric '+' operations must either be both bigints or both numbers.",
       "id": "bigintAndNumber",
     },
     "range": {
@@ -3312,7 +3328,8 @@ exports[`TSGoLint E2E Snapshot Tests > should generate consistent diagnostics sn
     "file_path": "fixtures/basic/rules/restrict-plus-operands/index.ts",
     "kind": 0,
     "message": {
-      "description": "Invalid operand for a '+' operation. Operands must each be a number or string, allowing a string + any of: \`any\`, \`boolean\`, \`null\`, \`RegExp\`, \`undefined\`. Got \`never\`.",
+      "description": "Invalid operand of type 'never' for a '+' operation.",
+      "help": "Operands must each be a number or string, allowing a string + any of: \`any\`, \`boolean\`, \`null\`, \`RegExp\`, \`undefined\`.",
       "id": "invalid",
     },
     "range": {