fix(ledger): no signer breaking homepage

[kyranjamie]

Try out Leather build 41a3e3d — Extension build, Test report, Storybook, Chromatic

Uses Loader pattern to prevent importing hook that instantly breaks the wallet when there's no data.

Nested loaders are very ugly, and we could alternatively make a double one for both. But ugly is better than broken. We need build pages with the pattern of "Get the data you need safely via loader pattern (or another safe method), pass into your page" rather than assuming all data can be read via a hook.

[pete-watters]

I've tested this manually and it resolves the issue

[fbwoolf]

@kyranjamie the native segwit address is used in other places in asset-list, shouldn't we replace those with the loader too? I think I broke this adding the taproot address for Runes, but it seems hard to understand when the ns address was already being used. It appears the useCurrentAccountNativeSegwitAddressIndexZero has a check for the signer, so that was the diff here? Should I add the loaders around the BTC asset item here and remove the deprecated useCurrentAccountNativeSegwitAddressIndexZero?

[kyranjamie]

@fbwoolf recognise it's not a very consistent pattern, and open for removing. Would love to move away from the hooks entirely to a more robust pattern.

Should I add the loaders around the BTC asset item here and remove the deprecated useCurrentAccountNativeSegwitAddressIndexZero?

Yep, sounds good. Honestly, I'd remove BitcoinFungibleTokenAssetList entirely and just handle with loaders directly in AssetList. Doesn't do anything beyond prop passing.