KC-1335, KC-1336: Fix nsf-mkdir parent UID path resolution and get to return consistent folder JSON by name vs UID

[sshrushanth-ks]

Summary

Fixes nsf-mkdir and get --format json folder behavior. nsf-mkdir now resolves existing parent folder UIDs in paths instead of creating a folder named after the UID, while name-based paths continue to work. get returns the same folder JSON schema whether the folder is looked up by name or UID.

Changes

• Added _resolve_segment() to resolve known NSF folder UIDs globally before falling back to name lookup via _find_existing_child()
• Prevents paths like tY6D-RanxY252zzBY_xU4A/My Child Folder from creating a folder named after the UID
• Name-based paths (e.g. Engineering/New Folder KD 1 June) still resolve parent folders by name and create intermediate segments when needed
• Updated nsf-mkdir parser help to document parent segments as folder names or UIDs
• Added/updated unit tests in test_nested_share_folder.py (test_mkdir_resolves_parent_uid_in_path, name-path and intermediate-segment cases)
• Pointed mkdir test mocks at folder_commands._nsf.create_folder_v3 to avoid lazy-import caching issues
• When a single folder is matched by name, recurse into execute() with the resolved folder UID instead of building a minimal inline JSON payload
• Name and UID lookups now share the same folder JSON builder (classic_folder, path, parent_uid, folder, records, etc.)
• Added test_get_user_folder_json_consistent_by_name_and_uid in test_command_record.py