Inconsistent formatting for event type properties

Nobody has claimed this yet.

In the [event types API reference page](https://docs.mapbox.com/mapbox-gl-js/api/events/), some event types list their properties as "properties" (MapBoxZoomEvent, MapDataEvent) and others as "Instance Members" (MapTouchEvent, MapMouseEvent, MapWheelEvent). They have considerably different UI, with the former appearing as text before the example and the latter as a list of dropdown boxes below it.

This is because they have inconsistent JSdoc labels in the [source](https://github.com/mapbox/mapbox-gl-js/blob/main/src/ui/events.js). MapBoxZoomEvent and MapDataEvent (both custom TS types) are annotated with the `@property` JSdoc label. Example:

```
* @typedef {object} MapBoxZoomEvent
* @property {MouseEvent} originalEvent The DOM event that triggered the boxzoom event. Can be a `MouseEvent` or `KeyboardEvent`.
```

This appears like:

The other three events are classes, and are annotated with a comment over each property:

```
/**
* The DOM event which caused the map event.
*/
originalEvent: TouchEvent;
```

This appears as the following:

As a further complication, some properties have extensive documentation including their own examples.


Most users presumably don't care if they're working with TS types or classes and would benefit from consistency in the documentation.

Three ideas about how to fix this:

- List all of the properties with `@property`
- I think this syntax is cleanest in the source code.
- This would create UI issues with larger properties. Could we configure the doc to view properties in dropdowns?
- List all of the properties in individual comments
- Dropdowns for all properties might be an improvement.
- It doesn't seem technically correct to refer to TS type classes as "Instance Members."
- Keep the source as is but configure JSDoc to make the styling more consistent.
- E.g. both properties and instance members after the example and in dropdowns.
- I'm not sure what's possible here.

Start with the event definitions in src/ui/events.js and compare the generated entries on the event types API reference page. Review how @property annotations and commented class properties become “properties” and “Instance Members,” then choose a consistent presentation that handles extensively documented properties. Done means the affected event types use the same understandable UI in the generated reference.

Written by the indexing model from the issue text.