[types] Add JSDoc based on website docs

[MysteryBlokHed]

Related to #424

This is a work-in-progress PR to add documentation from the website to the types. This will not only allow for better developer experience by providing more informative in-editor documentation, but will also allow the docs to be auto-generated with a tool like TypeDoc in the future.

I've started by adding docs for the Hooks and ColorSpace classes, but docs for other classes/functions/properties should be added too.

If there are any classes or functions in particular that anyone thinks should have documentation brought over from the website, I'm open to suggestions. Some things seem relatively self-explanatory with their types, so I don't think that every method and property needs to include super-detailed docs.

Note: In the toGamut.d.ts file, I did actually modify the types themselves a bit in order to make them more accurate, and to make it easier to access the types for the function's options.

[netlify]

✅ Deploy Preview for colorjs ready!

Name	Link
🔨 Latest commit	5bc5c01
🔍 Latest deploy log	https://app.netlify.com/sites/colorjs/deploys/65d249a27127dd0008cc8b52
😎 Deploy Preview	https://deploy-preview-436--colorjs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[MysteryBlokHed]

While not in the website, this could probably use some documentation for each property:

color.js/types/src/space.d.ts

Lines 4 to 27 in 4dcc46b

	export interface Format {
	type?: string | undefined;
	name?: string | undefined;
	id?: string | undefined;
	coords?: string[] | undefined;
	coordGrammar?: (string & { range?: [number, number] })[] | undefined;
	serializeCoords?:
	| ((coords: Coords, precision: number) => [string, string, string])
	| undefined;
	toGamut?: boolean | undefined;
	commas?: boolean | undefined;
	lastAlpha?: boolean | undefined;
	noAlpha?: boolean | undefined;
	test?: ((str: string) => boolean) | undefined;
	parse?: ((str: string) => ColorConstructor) | undefined;
	serialize?: ((coords: Coords, alpha: number, opts?: Record<string, any>) => string) | undefined;
	}
	export interface CoordMeta {
	name?: string | undefined;
	type?: string | undefined;
	range?: [number, number] | undefined;
	refRange?: [number, number] | undefined;
	}

[jgerigmeyer]

Looks good, thanks @MysteryBlokHed!

[MysteryBlokHed]

Oops, it looks like there's a formatting problem that made CI fail. I'll open a new PR to fix that.