feat(core): migrate group scoped name

[jimcase]

Description

Currently, each identifier has only 1 display name, and the entire wallet has a username which is shared with connections. In the new account based flow, this global username is being removed.

Instead:

• We will share the display name of individual identifiers

• Groups will have a group name (same as display name), and a “username” per group

  • The group name is shared with connections

  • The username is shared with other members of the group when setting up the group

Refactor defaultProfile to currentAccount

The selected profile is moved and refactored to stateCache, outside of Authentification Object, as it is independent of the auth. See here:

...
const initialState: StateCacheProps = {
  initializationPhase: InitializationPhase.PHASE_ZERO,
  recoveryCompleteNoInterruption: false,
  isOnline: false,
  routes: [],
  currentProfile: "",
  authentication: {
    loggedIn: false,
...

New methods:

setCurrentProfile()
getCurrentProfile()

New method file habName to parse the identifier names:

New format example: 1.2.0.3:theme:isInitiator-groupId-userName:displayName

parseHabName is a utility function designed to deconstruct a structured "hab name" string into its individual components. It takes a single name: string argument, which is expected to follow the format version:isInitiator-group_id-username:display_name. The function then parses this string and returns an object of type HabNameParts, providing programmatic access to extracted fields such as version, isInitiator (a boolean indicating if the current entity is the group initiator), groupId, userName, and displayName.

formatToV1_2_0_3 is a utility function that constructs a "hab name" string from its individual components, specifically adhering to the 1.2.0.3 version format. It takes an object of type HabNameParts (which contains fields like version, isInitiator, groupId, userName, and displayName) and serializes them into the precise string
format version:isInitiator-group_id-username:display_name.

Checklist before requesting a review

Issue ticket number and link

• This PR has a valid ticket number or issue: VT20-1972

Testing & Validation

• This PR has been tested/validated in iOS, Android and browser.
• Added new unit tests, if relevant.

Design Review

• [] In case this PR contains changes to the UI, add some screenshots and/or videos to show the changes on relevant devices.