Ampersand escapes in text content handled differently to JSX

## Reproduction

With the following code:

```
import htm from "https://unpkg.com/htm@2.1.1/dist/htm.mjs";
import { h } from "https://unpkg.com/preact@8.4.2/dist/preact.mjs";
const html = htm.bind(h);

console.log(html`

`)
```

I get a VNode with `.children = ["<"]` — i.e. what I mean to render as `<` gets rendered as `<` instead.

## Expected results

Testing this in JSX via say , `

` gets transformed into `h("div", ["<"]);` as I originally expected.

I haven't poked into how they are doing this… seems like something that ultimately relies on a lookup table.

## Workaround

I am able to escape via string interpolation (e.g. `${'<'}` instead of `<`). Changing the last line in my sample code to:

```
// …

console.log(html`

`)
```

Results in a VNode with `.children = ["<"]` as I need. Is this the recommended style?

Start with the tagged-template entry point shown in the reproduction: htm.bind(h) and the text content inside the template. Compare how literal ampersand escapes and interpolated strings are tokenized, using the provided VNode output as the baseline. Done means text entities such as < produce the corresponding decoded text, consistently with JSX, without breaking interpolation.

Written by the indexing model from the issue text.