Update a flow and changing id or namespace failed about kestra HOT 2 CLOSED

The ui logic must follow backen constraints. So we have to define the appropriate behavior.

For this issue we can :

• Allo id change ( which is obviously not what is possible and desired now)
• Clone flow with new name ans ns on clone operation
• Clone and delete flow
• Manage virtual flows or allow id change on revision update which seems complicated and looks like a trap

I think the best way to do this is clone only. Ask new id when operation is in progress.
This prevent existing flow and it's exexution to be deleted. conservative approach is often good ans we may disable some unwanted flows.
We should avoid complex user data management to keep sustem ux as kiss as possible.

Also I really think description in flow should be quite mandatory : it forces self documentation and legacy flow easier to manage.

from kestra.

Maybe I'm not clear but the idea is to forbid the edition of namespace and Id.
On the #60, we are going on further

from kestra.