fix: accept newline-separated seed words in import (fixes #3128)

[TeapoyY]

Summary

Fixed the seed word import to accept both newline-separated and space-separated input formats.

Changes

1. src/components/wallet/seedwords/components/Edit.tsx

Updated the SEEDWORD_REGEX to:

• Accept multiple whitespace characters (spaces, newlines, tabs) between words: \s+ instead of \s
• Allow leading and trailing whitespace: ^\s* and \s*$

Before: /^(([a-zA-Z]+)\s){23}([a-zA-Z]+)$/
After: /^\s*(([a-zA-Z]+)\s+){23}([a-zA-Z]+)\s*$/

2. src/components/wallet/seedwords/SeedWords.tsx

Changed handleApply to split by any whitespace instead of just spaces:

Before: data.seedWords.split(' ')
After: data.seedWords.trim().split(/\s+/)

This correctly handles:

• Space-separated: word1 word2 word3 ...
• Newline-separated: word1\nword2\nword3...
• Copy-pasted text with mixed whitespace
• Text with leading/trailing whitespace

Root Cause

1. The original regex \s only matched single whitespace characters. Multi-line input with newlines between words could cause the pattern to fail in edge cases.
2. The split(' ') only split on space characters, not on newlines or tabs, so newline-separated input would produce an incorrect word array.

Acceptance Criteria (from issue)

• Seed word import handles words entered one per line (newline-separated) in addition to space-separated
• Seed word import works correctly when copy-pasting the full phrase
• The confirmation tick becomes available once valid seed words are detected, regardless of whitespace format

Closes #3128

[gemini-code-assist]

Code Review

This pull request improves the robustness of seed word input by allowing multiple whitespace characters and trimming leading or trailing spaces in both the processing logic and the validation regex. A review comment suggests further normalizing the input to lowercase to prevent issues with case-sensitive wordlists.

[gemini-code-assist]

It is a good practice to normalize seed words to lowercase before processing them. This prevents potential issues with the backend if it expects a strict lowercase wordlist (like BIP-39) and handles cases where users might have accidental capitalization from mobile keyboards or copy-pasting.

Suggested change

	setNewSeedWords(data.seedWords.trim().split(/\s+/));
	setNewSeedWords(data.seedWords.trim().toLowerCase().split(/\s+/));