Multi-environment support, GraphQL, EventHandlers, and Local provider!

This release contains a bunch of new exciting features that makes Booster easier to use and more powerful:

New features

• Added support for GraphQL
  The idea is to move towards GraphQL where:
  • Commands are submitted through mutations
  • ReadModels read requests are submitted through queries
  • You can subscribe to ReadModels changes through subscriptions
    Right now, the GraphQL schema is generated automatically based on your Commands and ReadModel types and you can submit mutations and queries using the endpoint /graphql. Subscriptions will come in a future release
• Event handlers: Now you can execute additional logic as a reaction to any event in your system, which in turn, can generate new events. This extends substantially the kind of application you can build.
• Multiple environments: Now, when you configure your Booster application in the config.ts file, you specify the name of the environment you are configuring. This way, for example, you can have a "production" environment that uses the AWS provider and a "development" environment that uses the local provider (see below)
• Local provider: There is a new provider available: 'framework-provider-local`. Its purpose is to allow you to execute Booster locally so that you can test and debug the application before sending it to production. Right now, only authentication and submitting commands are supported. We will keep working on it to make it support all Booster features

Bugfixes

There were so many bugs fixed that writing them here will take too long. I'd rather spend that time fixing more bugs! 😄