fix(bug): fix staking console log

[varun-doshi]

Fixes #449

[Copilot]

Pull Request Overview

Update console log messages to display staking amounts as human-readable decimal values instead of raw U256 divisions.

• Convert U256 stake values to f64 and divide by 10^18 for display
• Applied change in three separate staking approval prompts

[Copilot]

The conversion from U256 to f64 via to_string() and parse is duplicated in multiple prompts. Consider extracting this logic into a shared helper (e.g., format_token_amount) to reduce repetition and improve readability.

[Copilot]

Using unwrap_or(0.0) will silently fallback on parse errors, potentially hiding conversion issues. It would be safer to handle parse errors explicitly or ensure the stake string is always a valid number.

Suggested change

	stake.to_string().parse::<f64>().unwrap_or(0.0) / 10f64.powf(18.0)
	match stake.to_string().parse::<f64>() {
	Ok(parsed_stake) => parsed_stake / 10f64.powf(18.0),
	Err(_) => {
	Console::user_error("Failed to parse stake value as a number.");
	return Err(ProviderError::InvalidStakeValue);
	}
	}

[Copilot]

Converting large U256 values to f64 can lose precision or overflow, leading to inaccurate amounts. Consider using a decimal or big-number formatting library to preserve full precision.