[remote signing]: walletrpc.ImportTapscript behaves differently in remote-signer vs. normal signing mode #10120
Description
Background
The issue was originally reported here, causing issues with running tapd connected to an lnd node that runs in remote-signer mode: lightninglabs/lightning-terminal#1123
The root cause was tracked down to be a different behavior of the walletrpc.ImportTapscript RPC in the remote-signing mode.
PR #10119 demonstrates this difference.
The root cause is somewhere in the btcwallet repository. Somehow importing tapscript addresses is handled differently based on whether the wallet is in watch-only mode or not.
Expected behaviour
An address imported with walletrpc.ImportTapscript should always end up in the "imported" wallet account, independent of whether the wallet is running in watch-only mode or not.
Actual behaviour
When btcwallet is running in watch-only mode, an address imported with walletrpc.ImportTapscript ends up in the "default" account.