Fix bugs initializing stretched and pasted tables.

[btrewern]

This fixes the following:

• Table is not initialised correctly if stretch is selected.
• Cannot correctly stretch pasted table.

[neSpecc]

explain why this line is needed in jsdoc, please

[btrewern]

I added a comment.

[Copilot]

Pull request overview

This PR aims to fix stretch-related initialization problems for the Editor.js table tool, ensuring that tables render with the correct “stretched” state and that tune changes properly update the block UI/state.

Changes:

• Add a rendered() lifecycle hook to apply the saved/configured stretched state after mount.
• Centralize tune UI/state updates in _updateTunes() and trigger block change dispatch on tune toggles.
• Initialize stretched explicitly in onPaste() data reconstruction.

Comments suppressed due to low confidence (1)

src/plugin.js:254

• After pasting, the code re-renders by replacing this.table.wrapper with this.render(), which returns a new outer block container. That nests a new block container inside the existing one and also leaks global listeners because the old Table instance isn't destroy()ed before being orphaned. Rebuild only the Table wrapper (destroying the old instance first) and then re-apply the block stretch state so paste doesn't leave the UI/data out of sync.

      withHeadings: firstRowHeading !== null,
      stretched: false,
      content
    };

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[btrewern]

I can't paste one table over another so the above seems to be irrelevant.