Ezrules

* Ability to backtest rule changes: make change, submit for backtesing, check result
* Switch to pydantic-based settings management
* Transaction submitted for testing are now saved in the history table
* Rule evaluation results are now saved in the history table
* new cli utilities to generate test data

* The app is compatible with AWS EKS
* Basic testing introduced
* Rule history is maintained through a history table
* Standalone scripts to init the db and add a user
* Internall, switch to poetry dependancy management
* Manager and evaluator can run as executables

* RDBMS are now supported as a backend for rule configuration storage
* The application can now be deployed in a k8s cluster

* At-notation is available. Constructs of type `if $send_country in Latam...`
* Users are now required to login to make changes to the rule set

* Dollar-notation can be used to refer to attributes, e.g. `if $amount>1000...`
* When you create a rule, you can now test it right away before deploying
* Outcomes of rules are now controlled against a list of allowed outcomes
* When a rule is edited, there is now a warning that someone else is working on it too
* Each rule revision now has a timestamp associated with it
* For rules with modification history, see the changelog with highlighted diffs