[Contract] Strengthen `liquidity_vault` into a reusable protected-execution primitive

[Solomonsolomonsolomon]

Evolve the current protected-swap pattern into a generic contract component for enforcing intent-versus-market checks across vault and strategy actions. This should become a reusable safety primitive rather than a narrowly scoped example.

[Martins-O]

@Martins-O has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Martins-O to this issue.

[adelekevictor12]

@adelekevictor12 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I will like to handle this task

ℹ️ Repo Maintainers: To accept this application, review their application or assign @adelekevictor12 to this issue.

[amanosiadnan-cmyk]

@amanosiadnan-cmyk has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hii, i'd like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @amanosiadnan-cmyk to this issue.

[SamixYasuke]

@SamixYasuke has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer, I’d refactor liquidity_vault into a generic protected-execution primitive rather than a swap-specific helper by separating execution intent validation, market condition checks, and asset movement into reusable components.

Concretely, I’d extract a core ProtectedExecution interface that:

• Accepts an execution intent (amount, direction, constraints)
• Runs pre-execution guards (price bounds, slippage limits, oracle staleness, tick validation)
• Evaluates market conditions at execution time
• Only then allows vault/strategy operations to proceed

ℹ️ Repo Maintainers: To accept this application, review their application or assign @SamixYasuke to this issue.