v1.6.0

fix: drop statement_id. Low value and has issues @dudymas (#64)

what

• remove the statement_id from the aws_lambda_permission resource for
  buckets

why

• statement_id breaks when valid buckets are specified. The two have entirely
  different requirements for what is syntactically valid
• statement_id is intended for organizing many documents. Since the
  permission is simple and its intent direct... the parameter is unneeded
• The alternative, to devise a way to correct valid bucket names, is more
  logic to maintain and could end up breaking again in the future.

references

• statement_id
• SweetOps thread (Public slack)