fixes/improvements/docs

[huntabyte]

• Widens the type for the various utils that accept an element/element getter as a prop from MaybeGetter<HTMLElement | undefined> to MaybeGetter<HTMLElement | null | undefined>
• Updated public methods in classes to arrow functions to avoid the dreaded this situation
• Explicit types/return types for public interfaces
• Some documentation improvements/additions
• Created a new internal DemoNote component to use to provide footnotes in small text under the demos.

[changeset-bot]

🦋 Changeset detected

Latest commit: 2f6e8be

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
runed	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
runed	✅ Ready (View Log)	Visit Preview	2f6e8be

[abdel-17]

I don't agree with using arrow functions for everything. It kind of defeats the purpose of using classes. If you need it pass it down, you can just create the arrow fn yourself.

() => something.foo()

It's a quirk with classes in JS, but it's expected. Built in classes behave like this.