look into including the underlying in the text search

[gmbronco]

No description provided.

[gmbronco]

original message from Bruno:

Hey team :wave::skin-tone-2:
While investigating an issue, I searched for wUSDL in the UI expecting it to return pools with wUSDL.
It missed a [boosted pool](https://balancer.fi/pools/ethereum/v3/0x10a04efba5b880e169920fd4348527c64fb29d4d) where wUSDL is the underlying token
I’m assuming the search algo is considering only pool tokens and not underlying tokens
Can we adapt to also consider the underlying?

this edge case comes from the fact, that FE is using different symbols for displaying purposes and different for adding liquidity to the pool. "wUSDL" is used only for adding liquidity, and search by USDL, or csUSDL – symbols used for displaying finds the pool without any issues.

to include the underlying in the search, we would need to add another join to the pool token for the underlying token, so the whole pools query will becomes slower. Also underlying token can have another underlying token, or pool resulting in even more complexity to cover. My recommendation is to keep things simple and allow to sacrifice searches for hidden information and stick to what is shown in the UI only.