Question about focus-order-semantics logic

### Product

axe-core

### Question

I was looking into the [focus-order-semantics](https://dequeuniversity.com/rules/axe/4.5/focus-order-semantics) rule and found a minimal diff where one has a violation and the other doesn't, but I can't figure out why. Any insight would be helpful, both into the rule's logic and if one actually does have an accessibility issue the other doesn't. (Note: I'm using v4.5.2 but from looking at the release notes for v4.6.X I don't think this behavior has significantly changed.)

The first treegrid's row raises a violation, but re-implementing the same thing with HTML table elements doesn't raise a violation. These seem to have the same accessibility tree, and they seem to behave the same way when I interact with them with the various assistive tech I have access to, which makes me expect either they'd both raise a violation or neither would.

# Code
```html

[role="treegrid"] {
border: solid;
width: fit-content;
}

[role="row"] {
display: block;
width: 100px;
}

Github

```

# Accessibility Tree
Taken from Chrome's devtools's accessibility tree view.

* treegrid "Navigation" focusable:true multiselectable:false readonly:false required:false
* row "Github" focusable:true selected:true
* gridcell "Github" readonly:false required:false
* link "Github" focusable:true
* staticText "Github"
* InlineTextBox ""