`space init` should not override profile

[sttts]

What happened?

Today space init overrides the up profile. The up profile is most likely the cloud profile for many ppl trying Spaces for the first time. In any case, it means dataloss if there is a profile already.

The expected behaviour would be to add a new profile under another name.

How can we reproduce it?

$ up login # log into cloud
$ up space init

After this the cloud login is lost.

What environment did it happen in?

Latest master version.