Pin aws_lambda_events dependency to patch versions

If you already have a version of aws_lambda_events in your project, and you update lambda_http, the events package's version might not be updated. This can cause compilation issues like the ones we saw in #471. With this change, the events package will be update with new patch versions, which should prevent issues like that from happening.

Author: calavera

lambda-http/Cargo.toml

@@ -17,7 +17,7 @@ travis-ci = { repository = "awslabs/aws-lambda-rust-runtime" }
 maintenance = { status = "actively-developed" }
 
 [dependencies]
-aws_lambda_events = { version = "^0.6", default-features = false, features = ["alb", "apigw"]}
+aws_lambda_events = { version = "^0.6.3", default-features = false, features = ["alb", "apigw"]}
 base64 = "0.13.0"
 bytes = "1"
 http = "0.2"
@@ -32,4 +32,4 @@ query_map = { version = "0.5", features = ["url-query"] }
 log = "^0.4"
 maplit = "1.0"
 tokio = { version = "1.0", features = ["macros"] }
-tower-http = { version = "0.2", features = ["cors"] }
+tower-http = { version = "0.2", features = ["cors"] }