Allow Region to be specified in DynamoDBCrudPolicy

[cdaley0]

The DynamoDBCrudPolicy currently only allows the table name to be configured. The region is always assumed to be the same region as the resource being deployed. We should be able to override the region in order to easily allow e.g deploying a lambda that can access a dynamodb table in a different region like so:

"DynamoDBCrudPolicy": {
  "TableName": {
    "Ref": "MyDynamoDBTableName"
  },
  "Region": {
    "Ref": "us-west-2"
  }
}

I'm aware that I can manually copy + paste the expanded definition for DynamoDBCrudPolicy into my SAM template, but allowing the region to be specified as proposed will make things easier.

[roger-zhangg]

Thanks for reporting, we will investigate and then track this as a feature request.