penalty from src validator happened during re-delegation period must be covered by unpairing insurance.

this option can make epoch periods as very fast

* remove possibility of out of index error by using map and re-create slices
* not allow re-delegation if src validator is in unbonding period
* not track re-delegation info if src validator is unbonded because it completes re-delegation immediately
* refactored tombstone related code - remove redundancy
* fix some minor logics in testing codes

includes minor refactoring

it does not return error

* coins must not contain any empty elements. so append it dynamically, not using fixed length of slice.

* only add positive amt

* check every coins are valid before sending it

* finally check inputs and outputs (should not trigger any error)

* add validity check before sending coins

* the destination(=output) is just a reward pool so we don't need to use InputOutputCoins. SendCoins will be ok.

* snedAmt must be positive
* refundCoins must be valid
* lsTokensToBurn must be valid to burn it
* sendCoins must be valid to send it to undelegator

even if insurance is paired, if it have invalid validator it must be out.

when creating candidates, we don't have to panic. just don't including it will be enough.

if insurance can cover penalty, unstaker will get penalty amt of tokens .
if not, reward module account get penalty amt of tokens. in this case, unstaker will get refunded ls tokens instead.

remove wrong encoding and use valid one
chain id must be foramtted as to pass validation of ethermint.

maybe delegation share's token value is higher than chunk size. In that case, just follow zero penalty flow.

we just return chunk un-delegated chunk balance to un-delegator

covered edge case where re-delegation penalty is bigger than un-pairing insurance's balance

* simplified variable names
* diet code lines
* make a function for common logic

and fix endblocker sequences in app.go which operates during EnableAdvanaceEpoch is on

if valid insurance is finished its duty, then it can be Pairing insurance again.

…name

updated invariance too.
hard to guarantee unstkaing amt always be gte than chunk size tokens

…ulation

# Conflicts:
#	app/app.go
#	app/sim_test.go
#	app/state.go
#	x/liquidstaking/keeper/liquidstaking.go
#	x/liquidstaking/keeper/liquidstaking_test.go