fix: changes on queryIncosistencyValidator in HardwareDetails to avoid refetch loop

[gustavobtflores]

Description

This PR changes useQueryInconsistencyInvalidator in HardwareDetails that could re-trigger continuously due to unstable navigateParams and expected count mismatches during tree/commit filtering, causing repeated invalidations/requests.

Closes #1710

[MarceloRobert]

Looks good, but it seems like it's still duplicating some requests. On the local db, it duplicates if I access hardwareDetails through the new listing, and on the production db, it duplicates when I change the commit of a tree via the selector of the treeTable (usually happens on mainline tree that has more data), but it's not in every hardware

[gustavobtflores]

Looks good, but it seems like it's still duplicating some requests. On the local db, it duplicates if I access hardwareDetails through the new listing, and on the production db, it duplicates when I change the commit of a tree via the selector of the treeTable (usually happens on mainline tree that has more data), but it's not in every hardware

It seems just useQueryInconsistencyInvalidator working as intended at first, I think we could work on having this inconsistencies fixed on another issue

[MarceloRobert]

It seems just useQueryInconsistencyInvalidator working as intended at first, I think we could work on having this inconsistencies fixed on another issue

Have you tested to check if it really isn't related to useQueryInconsistencyInvalidator? If so then ok, I'll create another issue and we can close this PR

[gustavobtflores]

It seems just useQueryInconsistencyInvalidator working as intended at first, I think we could work on having this inconsistencies fixed on another issue

Have you tested to check if it really isn't related to useQueryInconsistencyInvalidator? If so then ok, I'll create another issue and we can close this PR

yeah, I have tested it, useQueryInconsistencyInvalidator is yet triggering because sometimes divergences still occur, but as I said before, we need to work on fixing this divergences

[MarceloRobert]

yeah, I have tested it, useQueryInconsistencyInvalidator is yet triggering because sometimes divergences still occur, but as I said before, we need to work on fixing this divergences

Ok then. Can you create an issue for that? We always need to have issues to track what needs to be done and when a problem has been seen.

nit: in this case in your phrase you should use 'still' instead of 'yet', I've noticed it other times too 😬

[MarceloRobert]

LGTM, fixes a piece of this problem puzzle