Rename lifecycle's name

Support renaming a lifecycle's name as per the UX designs.

• Initial design
• Initial walkthrough

Proposal

Option 1

We could use the existing updateLifecycle mutation to handle the name change, but keep in mind that it supports multiple operations (e.g. creating/deleting/setting default statuses) and requires the full dataset from the UI. This increases the risk of unintentionally modifying or deleting statuses, or changing default values.

Option 2 (preferred)

We could consider adjusting updateLifecycle to prevent unintentional changes when statuses and their default index positions aren't included in the payload.

1. Add name argument
2. Ensure no changes are applied when statuses or any of the default_X_index arguments are missing.

Option 3

It might be worth introducing a simpler mutation that only updates lifecycle attributes like the name.