Fix inconsistencies between swaps store slippage and shared value

[walmat]

Fixes APP-2255

What changed (plus any additional context for devs)

1. Swap Navigation Parameters Enhancement

State Management

• Added slippage parameter handling in getSwapsNavigationParams
• Improved default value handling for input/output assets
• Added chainId fallback to mainnet

Parameter Processing

• Added validation for slippage parameter
• Implemented conversion from basis points to string format
• Added integration with remote config for default slippage values

Code Organization

• Moved state retrieval to top of function
• Consolidated asset parameter handling
• Added proper type safety for parameters

2. Swap Provider Updates

State Management

• Removed direct worklet call for default slippage
• Now uses navigation parameters for initial slippage value
• Maintained existing haptics and analytics integration

Code Cleanup

• Removed unused imports
• Simplified parameter initialization
• Improved type definitions

This PR improves the swap navigation parameter handling by adding proper slippage management and better state organization while maintaining existing functionality.

Screen recordings / screenshots

Simulator.Screen.Recording.-.iPhone.16.Pro.-.2025-01-14.at.12.24.57.mp4

What to test

test swaps on different chains and see the minimum value received changes with the slippage change

[linear]

APP-2255 Issue: User's Slippage rates were incorrect from the original slippage set

[brunobar79]

Launch in simulator or device for 0413473

[derHowie]

lgtm

[maxbbb]

Adding the ability to set the slippage in the route params is good but none of the current routes to swaps were trying to do that, and the fallback logic is the same as before so I'm not understanding how this fixes the linked issue.

[walmat]

Adding the ability to set the slippage in the route params is good but none of the current routes to swaps were trying to do that, and the fallback logic is the same as before so I'm not understanding how this fixes the linked issue.

That wasn't the issue. The issue was with the shared value and swaps store value being out of sync with one another, which is fixed in this PR. That deeplink / route param fix is just another one I noticed during investigating.

[brunobar79]

Launch in simulator or device for d11ea69