issues-go/issues/feat: implement "renaming"/description

There isn't a good way to "rename" variadic's via the tui

---
It wouldn't be too hard to add a method of varifying that the state of the variadic on disk mirrors the variadic in memory. For example, when writing a variadic, remove any existing fields that are not mirrored in memory.

This would require some amount of confirmation from the user before we "delete" the previous state.

---
This is not just for variadics, this spreads across the project - even to the entire Issue object. It *might* be worth it to implement separate logic for renaming Issues.