Prepopulate LPNFT denoms in view server

[hdevalence]

Is your feature request related to a problem? Please describe.

The view server fetches denoms from the chain, but LPNFT denoms aren't registered with the chain, because they're mostly only relevant to the user who actually controls the LPNFT, so they won't be found in the lookup.

There are four denoms for each position ID, one for each position state:

LpNft::new(id, position::State::Opened).denom()
LpNft::new(id, position::State::Closed).denom()
LpNft::new(id, position::State::Withdrawn).denom()
LpNft::new(id, position::State::Claimed).denom()

When the view server downloads a full transaction, it should, for each PositionOpen action, grab the position ID out of the action, compute the four denoms, and save them locally.