fix: assert uniqueness by origin (#3298)

[audreydng]

Fix test_screens to handle duplicate monitor names on Linux Wayland by asserting uniqueness on origin instead of name, and skip the screen[0] == (0, 0) check on Linux Wayland since it is not guaranteed.

Fixes #3298

PR Checklist:

• I will abide by the BeeWare Code of Conduct
• I have read and have followed the CONTRIBUTING.md file
• This PR was generated or assisted using an AI tool.

[freakboy3742]

Thanks for the PR. Looks like you've found a good workaround to the problem described by the original ticket.

The only feedback on the PR is that we try to avoid having platform-specific details in the testbed tests themselves, instead describing platform-specific details in terms of properties that individual probes can enable or disable as required.

However, in this case, I don't think there's a need for that. As noted inline, the key detail we need to assert is that the monitor origins are unique - there's no hard requirement that one of them is at (0,0).

So - if you can remove the "optional (0,0)" test, and remove the reference to Wayland in the test comment, this should be good to land!

[audreydng]

Thanks for the PR. Looks like you've found a good workaround to the problem described by the original ticket.

The only feedback on the PR is that we try to avoid having platform-specific details in the testbed tests themselves, instead describing platform-specific details in terms of properties that individual probes can enable or disable as required.

However, in this case, I don't think there's a need for that. As noted inline, the key detail we need to assert is that the monitor origins are unique - there's no hard requirement that one of them is at (0,0).

So - if you can remove the "optional (0,0)" test, and remove the reference to Wayland in the test comment, this should be good to land!

Thanks for the feedback! I've removed the (0, 0) test.

[freakboy3742]

Thanks for that update - there was also a need to simplify the test comment; I've pushed an update to that effect (plus a simplification of the change note).

Thanks for the fix!