Make liquidity events consistent

[axionyu]

Description

The goal of this fix is to make the liquidity events more consistent - liquidity, tick_low and tick_high will be emitted for LiquidityAdded (Mint), LiquidityRemoved (Burn) and LiquidityModified. This is to ensure that the event emission logic is similar to Uniswap V3 (https://docs.uniswap.org/contracts/v3/reference/core/interfaces/pool/IUniswapV3PoolEvents#burn)

Referencing the Burn and Mint event there.

Note: I have also moved the UpdateLiquidityResult from the swap-interface pallet to the swap pallet. The reason is that the TickIndex is in the swap pallet. If I add the swap pallet as a dependency, it would result in a circular dependency so thus I decided to move it.

Related Issue(s)

• Closes #[issue number]

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• [x ] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Other (please describe):

Breaking Change

If this PR introduces a breaking change, please provide a detailed description of the impact and the migration path for existing applications.

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• [x ] I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• [x ] New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Screenshots (if applicable)

Please include any relevant screenshots or GIFs that demonstrate the changes made.

Additional Notes

Please provide any additional information or context that may be helpful for reviewers.