Configuration table linked variants are confused about fillet edges

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Problem description

Hi. I'm attaching a trivial reproducer of this problem. Recipe:

1. Load the attadched "tst.FCStd". This contains a single body: a plain box. The dimensions of this box are set from a configuration table in the Spreadsheet. One of the edges has a fillet. The body has a linked variant Body001. This is intended to be reconfigured from data in the configuration table, as described in the docs: https://wiki.freecad.org/Configuration_Tables
2. Click on the linked Body001
3. "Link Copy on Change" should already be "enabled". Choose a different "Configuration" than what's selected; I just chose "b"
4. Select "recompute". I see this working properly; the box grows bigger. "Link Copy on Change" changes to "Owned"
5. Set "Link Copy on Change" back to "Enabled", choose Configuration "c" and recompute again

At this point I usually see an error:

```
FeatureDressUp.cpp(209): Invalid edge link: ;#6d:2;:G;XTR;:H7e8:7,E.Edge5
Fillet003: Invalid edge link: ;#6d:2;:G;XTR;:H7e8:7,E.Edge5
```

Sometimes it's inconsistent, and I need to repeat step 5. Selecting the problematic Fillet003 in Body001 says that it applies to `?Edge5`: somewhere freecad lost track of which edge the fillet should work on. I can use the GUI to re-select the edge, which fixes it. But changing the configuration makes it break again.

I see similar issues with the SubShapeBinder.

Thank you very much

[tst.FCStd.txt](https://github.com/user-attachments/files/18494727/tst.FCStd.txt)

### Full version info

```shell
Debian gnu/linux. amd64. freecad=1.0.0+dfsg-5

OS: Debian GNU/Linux trixie/sid (xcb)
Architecture: x86_64
Version: 1.0.0.
Build type: Release
Python 3.13.1, Qt 5.15.15, Coin 4.0.2, Vtk 9.3.0, OCC 7.8.1
Locale: English/United States (en_US)
Stylesheet/Theme/QtStyle: unset/FreeCAD Classic/Qt default
Installed mods:
* LCInterlocking

```

### Subproject(s) affected?

None

### Anything else?

_No response_

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct