TA-4286: Add validation for git profile name

[Zgjim Haziri (ZgjimHaziri)]

Description

• Git profile name fails when we try to create it with restricted filename characters, since we use that name to create the file in which it will be stored.
• The simplest solution seems to be failing the creation with a descriptive validation error message.
• Other considered solutions required a larger refactoring effort or had downsides:
  • Using a UUID as the filename. This required changing the way we fetched the profile by reading the file and looking for the profile name in the content.
  • Sanitizing the name. Showed possible name conflicts scenarios, e.g. if we sanitize the character '/' with '_', then we can have a conflict if the user tries to create "test/1" and "test_1".
• Since the CLI user is aware of the files created in his environment, it seems reasonable to proceed with the solution.

Relevant links

• Jira: https://celonis.atlassian.net/browse/TA-4286

Checklist

• I have self-reviewed this PR
• I have tested the change and proved that it works in different scenarios
• I have updated docs if needed

Screenshots of the failure message

[Buqeta (Buqeta)]

Can we also increase the CLI version?

[Zgjim Haziri (ZgjimHaziri)]

Can we also increase the CLI version?

Will leave the bump in another PR, in order to release both of these fixes together.

Note: working on a release process for CLI now, will make this more clear there.

[Buqeta (Buqeta)]

Just remembered: can you add some tests for these changes?