Update several TreeView unit tests

[thatblindgeye]

Describe the enhancement or change
Followup to #9773, some tests could use some updating

• Update tests that are using getByText(...).tagName.toBe("BUTTON") so that they use getByRole("button") instead
• In TreeViewRoot, add tests for hasCheckboxes and hasSelectableNodes; should first try testing if pressing Tab focuses the correct element, otherwise try using a user.click event, otherwise just check that the tabindex attribute is applied to the correct element
• In TreeViewList, update the "Renders toolbar content when toolbar prop is passed" test to check that getByrole('separator') is in the doc, and update "Does not render toolbar content when toolbar prop is not passed" test to check that queryByText... is not in the doc
• check that any getByRole('button') calls are also passing in the {name: ...} options object

Is this request originating from a Red Hat product team? If so, which ones and is there any sort of deadline for this enhancement?

Any other information?

[wise-king-sullyman]

A few other things we might want to address in the TreeViewListItem tests

• we have a few tests where we're just asserting that a node has an attribute but not what the value of that attribute is, do we just not care what the value is in those instances? I would think we would assert about the value as well as the presence.
• In the callback tests when we're asserting that the callback isn't called when it shouldn't be we're interacting with the component but not passing the callback, shouldn't it be the other way around?
• the parentItem and useMemo props don't seem to be tested

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[thatblindgeye]

Some tests could be added per updates made in #10220

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.