Runtime: QA for renaming edge cases

[begelundmuller]

• [ ] Check graceful handling of changing a resource while rename is running
• [ ] Check reconcilers handle renames gracefully if not yet reconciled (no state set)
• [ ] ProjectParser: Check it doesn't attempt renaming to a name that already exists (should be a parse error)
• [ ] Check graceful handling of renaming a resource while rename is running
• [ ] Check reconcilers don't rely on the value of RenamedFrom – should only rely on state
• [ ] Prevent cancelled reconciler for a resource from running at the same time as the rename is running (not caught by DAG or name checks due to rename, must check RenameFrom)

[ericpgreen2]

This issue might be alluding to it, so I'll leave this here – I just ran into this error in Rill Developer:

1. I renamed my_source to my_source_2
2. I renamed my_source_2 back to my_source
3. I got this error: "Name my_source is already in use"

It seems waiting 1-2 minutes frees up the name again, but it's not available on the order of seconds.