feat(amm)!: add transaction deadlines to swap and liquidity instructions

All mutable AMM instructions now require a `deadline: u64` field (Unix
timestamp in milliseconds). Enforcement uses the LEZ-native timestamp
validity window set on ProgramOutput; the runtime rejects the
transaction if the sequencer submission timestamp is at or past the
deadline.

BREAKING CHANGE: AddLiquidity, RemoveLiquidity, SwapExactInput,
SwapExactOutput, and NewDefinition instruction variants now require a
`deadline` field.

Closes #8

artifacts/amm-idl.json

@@ -70,6 +70,10 @@
         {
           "name": "amm_program_id",
           "type": "program_id"
+        },
+        {
+          "name": "deadline",
+          "type": "u64"
         }
       ]
     },
@@ -131,6 +135,10 @@
         {
           "name": "max_amount_to_add_token_b",
           "type": "u128"
+        },
+        {
+          "name": "deadline",
+          "type": "u64"
         }
       ]
     },
@@ -192,6 +200,10 @@
         {
           "name": "min_amount_to_remove_token_b",
           "type": "u128"
+        },
+        {
+          "name": "deadline",
+          "type": "u64"
         }
       ]
     },
@@ -241,6 +253,10 @@
         {
           "name": "token_definition_id_in",
           "type": "account_id"
+        },
+        {
+          "name": "deadline",
+          "type": "u64"
         }
       ]
     },
@@ -290,6 +306,10 @@
         {
           "name": "token_definition_id_in",
           "type": "account_id"
+        },
+        {
+          "name": "deadline",
+          "type": "u64"
         }
       ]
     },