Force interface instead of type for better docs (#3815)

Typescript's type aliases (`type X = thing`) can refer to basically
anything, which makes it hard to write an automatic document formatter
for them. Interfaces on the other hand are only object, so they play
much nicer with docs. Currently, object-flavoured type aliases don't
really get expanded at all on our docs site, which means we have a bunch
of docs content that's not shown on the site.

This diff introduces a lint rule that forces `interface X {foo: bar}`s
instead of `type X = {foo: bar}` where possible, as it results in a much
better documentation experience:

Before:
<img width="437" alt="Screenshot 2024-05-22 at 15 24 13"
src="https://github.com/tldraw/tldraw/assets/1489520/32606fd1-6832-4a1e-aa5f-f0534d160c92">

After:
<img width="431" alt="Screenshot 2024-05-22 at 15 33 01"
src="https://github.com/tldraw/tldraw/assets/1489520/4e0d59ee-c38e-4056-b9fd-6a7f15d28f0f">


### Change Type

- [x] `sdk` — Changes the tldraw SDK
- [x] `docs` — Changes to the documentation, examples, or templates.
- [x] `improvement` — Improving existing features

apps/docs/components/ArticleDetails.tsx

@@ -1,7 +1,7 @@
 import { Article } from '@/types/content-types'
 import { Icon } from './Icon'
 
-type ArticleDetailsProps = {
+interface ArticleDetailsProps {
 	article: Article
 }
 

apps/docs/components/ArticleNavLinks.tsx

@@ -2,7 +2,7 @@ import { ArticleLinks } from '@/types/content-types'
 import Link from 'next/link'
 import { Icon } from './Icon'
 
-type ArticleNavLinksProps = {
+interface ArticleNavLinksProps {
 	links: ArticleLinks
 }
 

apps/docs/components/Autocomplete.tsx

@@ -13,13 +13,13 @@ import './Autocomplete.css'
 import { Icon } from './Icon'
 import { Spinner } from './Spinner'
 
-export type DropdownOption = {
+export interface DropdownOption {
 	label: string
 	value: string
 	group?: string
 }
 
-type AutocompleteProps = {
+interface AutocompleteProps {
 	customUI?: React.ReactNode
 	groups?: string[]
 	groupsToIcon?: {