Fix the mutation setting of hierarchy-inert commands

[Fishbowler]

Proposed changes

Performance improvement.

Maestro performs assertions like assertNotVisible based on a timer tied to the last command that altered the hierarchy. We track that through a return value on a command that indicates whether the command mutated the hierarchy (or may have).

This change updates a few inert commands, marking them as non-mutating, which will speed up assertions that immediately follow them.

In the below example, assertNotVisible's timer should be from the tapOn, not from the last copyTextFrom.

- tapOn: Remove Foo
- copyTextFrom:
    id: thing1
- copyTextFrom:
    id: thing2
- copyTextFrom:
    id: thing3
- assertNotVisible: Foo

I've added comments on justifications, so that the next person visiting this code might be able to think a little less about these :)

Testing

e2e 🤞

Issues fixed

Fixes #3117