Fix enum naming to prioritize entity enums over ugly parameter names

Co-authored-by: abraham <3341+abraham@users.noreply.github.com>

Author: Copilot

dist/schema.json

@@ -14868,11 +14868,7 @@
               "type": "array",
               "description": "Specify the timeline(s) for which markers should be fetched. Possible values: `home`, `notifications`. If not provided, an empty object will be returned.",
               "items": {
-                "type": "string",
-                "enum": [
-                  "home",
-                  "notifications"
-                ]
+                "$ref": "#/components/schemas/FilterContextEnum"
               }
             }
           }
@@ -16186,7 +16182,7 @@
               "type": "array",
               "description": "Types to exclude from the results.",
               "items": {
-                "$ref": "#/components/schemas/GetApiV1NotificationsParamTypesEnum"
+                "$ref": "#/components/schemas/NotificationTypeEnum"
               }
             }
           },
@@ -16245,7 +16241,7 @@
               "type": "array",
               "description": "Types to include in the result.",
               "items": {
-                "$ref": "#/components/schemas/GetApiV1NotificationsParamTypesEnum"
+                "$ref": "#/components/schemas/NotificationTypeEnum"
               }
             }
           }
@@ -17970,7 +17966,7 @@
               "type": "array",
               "description": "Types to exclude from the results.",
               "items": {
-                "$ref": "#/components/schemas/GetApiV1NotificationsParamTypesEnum"
+                "$ref": "#/components/schemas/NotificationTypeEnum"
               }
             }
           },
@@ -17991,7 +17987,7 @@
               "type": "array",
               "description": "Restrict which notification types can be grouped. Use this if there are notification types for which your client does not support grouping. If omitted, the server will group notifications of all types it supports (currently, `favourite`, `follow`, `reblog` and `admin.sign_up`). If you do not want any notification grouping, use [GET `/api/v1/notifications`] instead. Notifications that would be grouped if not for this parameter will instead be returned as individual single-notification groups with a unique `group_key` that can be assumed to be of the form `ungrouped-{notification_id}`. Please note that neither the streaming API nor the individual notification APIs are aware of this parameter and will always include a “proper” `group_key` that can be different from what is returned here, meaning that you may have to ignore `group_key` for such notifications that you do not want grouped and use `ungrouped-{notification_id}` instead for consistency.",
               "items": {
-                "$ref": "#/components/schemas/GetApiV1NotificationsParamTypesEnum"
+                "$ref": "#/components/schemas/NotificationTypeEnum"
               }
             }
           },
@@ -18050,7 +18046,7 @@
               "type": "array",
               "description": "Types to include in the result.",
               "items": {
-                "$ref": "#/components/schemas/GetApiV1NotificationsParamTypesEnum"
+                "$ref": "#/components/schemas/NotificationTypeEnum"
               }
             }
           }
@@ -38708,21 +38704,6 @@
           "user_domain_block",
           "account_suspension"
         ]
-      },
-      "GetApiV1NotificationsParamTypesEnum": {
-        "type": "string",
-        "enum": [
-          "mention",
-          "status",
-          "reblog",
-          "follow",
-          "follow_request",
-          "favourite",
-          "poll",
-          "update",
-          "admin.sign_up",
-          "admin.report"
-        ]
       }
     },
     "securitySchemes": {