Add Execute step to the job definition

[tibkiss]

To greater flexibility, add an Execute step where the user allowed to enter custom lua statements.
The lua statements can define variables which will become available at Entry / Exit and Adjustment conditions
Initial design example:

"Execute": [
  { 
    "Schedule": {
      "Every": "5min"
    },
    "Statements": [
        "if underlying_price > leg_ll_strike then max_days_in_trade = 10 end"
    ] 
 },
 {
   "Schedule": {
     "Every": "post-trade"
  },
  "Statements": {
    "price_after_trade = underlying_price",
    "iv_after_trade = underlying_iv"
 }
]

[tibkiss]

Request related to this ticket from Teresa W:

  For example, I want to enter an entry condition to check to see of the current position's expiration_date is not equal to any of the other open positions' expiration_date?   My final goal is to not double up (initiate new trade) on the same Expirations from Old Lead Scout to new trade UNLESS the next available DTE is > 200. For example, if the youngest trade has a DTE at 158 days, do not double up the new trade at the 158 DTE. Choose the next DTE (like at 185 days, if available). But, if the next available expiration is 205 DTE, then double up on the 158 DTE expiration.