fix(lambda): use output_base64sha256 directly instead of function fil…

…ebase64sha256

"source_code_hash = filebase64sha256(data.archive_file.this.output_path)"
can be called before the "data.archive_file.this" resource has created
the zip file and may fails because the file does not exist.

The cause of the issue here is calling a function with a known argument,
the workaround would be to directly use the output_base64sha256
attribute of the data source instead of calling filebase64sha256.

this commit replaces the "filebase64sha256" function by the "output_base64sha256"

Thanks to @pvillaverde for pointing this out!

main.tf

@@ -260,7 +260,7 @@ data "archive_file" "this" {
 # Create Lambda function for stop or start aws resources
 resource "aws_lambda_function" "this" {
   filename         = data.archive_file.this.output_path
-  source_code_hash = filebase64sha256(data.archive_file.this.output_path)
+  source_code_hash = data.archive_file.this.output_base64sha256
   function_name    = var.name
   role             = var.custom_iam_role_arn == null ? aws_iam_role.this[0].arn : var.custom_iam_role_arn
   handler          = "scheduler.main.lambda_handler"