Improve JSDoc Types (Part 1)

[ITenthusiasm]

Description

This is an initial amount of work for improving the JSDocs in the codebase (as mentioned in #2241).

---

I figured it would make more sense to apply the JSDoc improvements incrementally. This has a few benefits:

• PRs end up being smaller to review (compared to if everything was done at once)
• Maintainers can more easily determine if [Feature]: Improve Project's JSDoc Types #2241 is worth pursuing (in case they want to cancel everything or only accept fragments of the work)
• Contributors can make progress more asynchronously (in case there are gaps in free time)

Note: If the preference is only to merge everything at once, then this PR can be kept in a Draft State until it is "sufficiently complete".

Additional Notes

When using JSDocs, TypeScript is fine with using String or string, * or any, and the like interchangeably. Not as idiomatic, but I'm not focused on that at the moment.

[lpinca]

Before you go any further, JSDoc comments should be kept as valid JSDoc, no TypeScript specific syntax.

[ITenthusiasm]

Noted. I'll try to see what I can do.

[ITenthusiasm]

For clarity, it seems like JSDoc supports Google Closure Compiler type expressions. Are we also interested in having those (e.g., generics via @template) here? Or no?

(I'm just trying to figure out what to remove/filter out, e.g., ConstructorParameters, Parameters, typeof.)

[lpinca]

I don't think @template exists in JSDoc.

[ITenthusiasm]

Okay. The PR has become somewhat anticlimactic, but I think that all of the TypeScript syntax should be gone now.

[ITenthusiasm]

The update to sendFrame is all that's left. Pretty simple 👍🏾

[ITenthusiasm]

Made the suggested change for createWebSocketStream. Can remove if desired.