fix(deps): rm jsdoc-to-markdown (vulnerable dep)

[DerekNonGeneric]

I am removing this dependency because it depends on unmaintained and vulnerable dependencies. One of them is the package put out by the JSDoc project, which has seemingly been abandoned. The package they used to publish now depends on a module w/ a CVE. To make matters worse, that vulnerable module has also been abandoned and does not appear to have any planned fixes. We can't wait for that whole ecosystem, so let's eliminate this dependency tree.

Refs: jsdoc/jsdoc#2013

Signed-off-by: Derek Lewis DerekNonGeneric@inf.is

/cc @jorgebucaran @smorimoto @yuvilio @septs as y'all might like to know — we're looking for a new docs generator (suggestions welcome)

[DerekNonGeneric]

ESDoc looks like a somewhat nice replacement for this but appears not to be able to understand the type space being proposed in the TC39 proposal for type annotations. That means that we would have to continue specifying them in the comment above the function signature and the type space after the colon.

I was not a fan of doing that previously but thought to bring it to y'all's attention (just found out about it myself).

Features

Generates good documentation.
Measures documentation coverage.
Integrate test codes into documentation.
Integrate manual into documentation.
Parse ECMAScript proposals.
Add custom features by [plugin architecture](https://github.com/esdoc/esdoc-plugins)
[ESDoc Hosting Service](https://doc.esdoc.org/)

[DerekNonGeneric]

We can hopefully continue to discuss in this thread and/or surface anything else relevant, but i am going to get this landed now since there is nothing really blocking it.