Need to implement unique folder/chat/prompt names validation and migration

[IlyaBondar]

We want to have unique folder/chat/prompt names on root level or inside parent folder.

What should be done:

• need to rename existing duplication names during migration to API storage (add postfix) - done in Automigrate conversations from local store (prev version) into stateful api (new version) #265
• need to add validation during rename: unique name in current folder, not allow empty names for chats, prompts, folders
• need to add validation during drag & drop: unique name in desctination folder
• not allow to use incorrect symbols in names (notAllowedSymbols). Pay attention on case when we autorename chat with first message(need to remove notAllowedSymbols, see also [Attachments] Need to forbid # symbol #592 )
• unique names for replay and playback (add postfix if need - see getNextDefaultName method)
• implement folder name limitation - 160 symbols (need to confirm, API storage key has limitation 1024 symbols (starting with entity type prefix i.e. from /<entity_type>/<bucket>/<path>)

Additionally:

• generate id for entites(see getPathToFolderById + generateConversationId) during import and regenerate folderId (see Need to integrate export/import with Stateful API #640 )

[VolhaBazhkova]

Verified on UAT server but it's needed to created proper test cases to pass them to Automation team