Astro.slots.render() docs should explicitly mention that component scripts are "consumed" by the first call

[TimonLukas]

(follow-up on #14042)

If a component receives slot content with Astro components and the slot is rendered multiple times (e.g. by repeated Astro.slots.render calls, or by calling Astro.slots.render while a <slot /> with the same name exists), only the first render will emit the scripts of the slotted components. Both of these examples will not be interactive:

---
const content = await Astro.slots.render('default')
---

<div class="some-component">
  <slot />
</div>

---
const firstContent = await Astro.slots.render('default')
const secondContent = await Astro.slots.render('default')
---

<div class="another-component">
  <Fragment set:html={secondContent} />
</div>

The Script processing docs mention this tangentially:

Deduplication: If a component that contains a <script> is used multiple times on a page, the script will only be included once.

When I first read this I assumed the deduplication to be a post-processing step, so the stateful nature felt surprising. IMO it would be helpful to explicitly mention this behavior in the Astro.slots.render docs, and maybe to clarify the Deduplication point quoted above.

For the Astro.slots.render docs, I'd propose to add something like this to the existing :::note:

This is for advanced use cases! In most circumstances, it is simpler to render slot contents with the <slot /> element. Once a slot has been manually rendered, any additional renders (both <slot /> and Astro.slots.render()) will not include <script> tags of slotted children, so make sure to emit the result of the first render using set:html instead.