Allow updating workspace names

[timroes]

What

Part of #9524

This will allow workspace names to be updated via the API, which we'll call as part of updating a cloud workspace later to keep both names in sync.

[benmoriceau]

LGTM; I would use this review to add the slug as well.

[benmoriceau]

I think that we can also use the review to update the slug as well.

[timroes]

Hi, thanks for pointing this out. I've made sure the slug is updated based on the new name. I assume we don't want (can't) let the user specifcy this, since the code we currenlty use anyway needs to "retry" until it's unique? Or would we want to let the API caller explicitly specify a slug and fail the request if that's already taken?

Could you also point me to a place the slug is used? It seems in URLs we're using the IDs of the workspace and not the slug?

[timroes]

I've changed the PR to actually pull the workspace renaming into a separate endpoint. The existing endpoint has a bit weird behavior that it requires a lot of the boolean flags to be set to udpate them. While I could make them optional it currently also has information like the notifications which are not required but if not specified will be updated to empty, which I assume is not what we want when calling this from cloud. Since I didn't want to break backwards compatibility now and potential usage of the API, I decided to pull it out into its own endpoint, that just handles the renaming of a workspace.

[benmoriceau]

LGTM, it is true that going with a new endpoint sounds better, especially since it could break external integration on which we don't have control.

[timroes]

@benmoriceau Would you mind giving this PR a review approval still, if it looks good for you, so GitHub will be satisfied :)