Bogus tab rendered after moving a container from a tabbed parent into another workspace

[WhyNotHugo]

Sway version

sway version 1.10.1

Debug Log

https://gist.github.com/WhyNotHugo/5b4f792f6bbd09138ed3d63ef22e1346

Configuration File

# Use this to `printenv SWAYSOCK` and then control sway from a non-child terminal.
exec foot

Description

When a split container is a child of a tabbed container, if the split container is moved to another workspace, its tab remains visible, and overlap the tab bar indefinitely; the tabs for the remaining children will be occluded by the leftover "floating" tab.

Reproduction steps

I suggest that you run a nested sway instance, run printenv SWAYSOCK and then run these command from non-child terminal. I use foot below, but any client which renders a single toplevel is good enough to reproduce this:

swaymsg exec foot
swaymsg exec foot
swaymsg exec foot
swaymsg layout tabbed
swaymsg focus left
swaymsg focus left
swaymsg focus right
swaymsg split h
swaymsg exec foot
swaymsg focus parent
swaymsg move container to workspace 9

The current workspace now has two tabs. The tab bar renders the two tabs, PLUS
the previous middle tab H[] overlapped with the two "real" tabs.

[WhyNotHugo]

Another symptom of this bug: if the tabbed container is converted into a horizontal split, that leftover tab remains visible, floating alone without a tab bar.