Fix edge-case errors when renaming nodes in scene tree

[SaracenOne]

Introduces the following rules to the standard NodePath fixer when renaming nodes in the scene tree:

• Disallow renaming in read-only resources.
• Disallow renaming of default properties in subscenes.
• Disallow renaming of properties and resources marked INTERNAL.

Animation NodePaths are marked as internal, but the updating of animation node paths (for animations which are editable), should still occur due to some special case handling for them. This just silences the warnings about broken NodePaths for the standard NodePath update pass.

Closes #83361

[KoBeWi]

Some of the issues you mentioned were fixed by #83263, so this might need re-assessing.

[SaracenOne]

Yeah, your PR would probably have fixed stuff, but it's still possible this PR may cover other edge cases. Denying the ability to update nodepaths for read-only resources may still make sense a general-purpose rule, but yours probably still covers the more obvious fail-cases. I'll leave it open in case its felt this still makes sense.

[KoBeWi]

I mean, the PR would still be useful if it fixes some remaining known issues. I didn't test, but the problems you described should've been fixed at least partially, so the PR and the linked issue should be tested if something still needs fixing.

btw it's still possible for properties with PROPERTY_USAGE_INTERNAL to be serialized and/or exposed in the inspector, skipping them might spawn new bugs.
The part about readonly stuff makes sense.

[SaracenOne]

Okay, I'll edit this to remove the PROPERTY_USAGE_INTERNAL stuff since your PR already fixed the most notable thing (animations) this PR was meant to address. The others are hypothetical fixes I discovered on the way, but I think they still make sense as rules that might avoid obscure edge-cases.