Improve variable naming in EditorInspector::update_tree

[npinsker]

Rename some variables to be more descriptive and move some that were far away from where they're used. No behavior change.

[AThousandShips]

Thank you for your contribution, we generally avoid these kinds of surface level changes without good reason, and many of these changes actively violate the comment style guidelines (including removing just the period from a number of comments)

The general philosophy for code comments is that they should help explain the code itself, and clarify things that might not be easy to get from the code, but code should be self explanatory, we don't use comments as documentation

Style concerns resolved

[AThousandShips]

As commented above I'd say that this PR shouldn't mix renaming variables or moving code with surface level changes, so comment changes should be separate from reordering or renaming variables, as changes to the code itself, even while it shouldn't affect behavior is something we should make sure we track well

Further strictly changing comments is very different and would be discussed far more so it'd hold back any other style changes, and might be rejected entirely on their own, we can also hide the comment changes from the history to make this PR less bad for the git history

[npinsker]

Thank you for the quick comments! Will remove the code comments

Resolved

[npinsker]

Thanks for the feedback -- I hope the PR's mildly helpful but regardless it is definitely extremely surface-level :) No worries if it isn't how you do things, feel free to reject

[Mickeon]

I actually am not against this, assuming the terminology is correct. The code being shifted brings it closer to where it's actually used, which makes the intent clearer. It does not functionally break.