provider/aws: Add aws_launch_configuration.enable_monitoring

[radeksimko]

Closes #479

I'm not convinced we should make this disabled by default. We had a similar situation in the past - when changing behaviour of egress rules in security groups where the default egress rule allowing all traffic was suddenly removed by default (and kept in the previous TF versions). This was BC, but it reality worst case scenario was that instances couldn't talk to the outside world -> de facto no direct data loss.

I don't think that disabling detailed monitoring suddenly is a good idea for people who rely on those data.

Nonetheless if anyone comes up with a meaningful reason why we should do the BC, I'm open.

Test plan

$ make testacc TEST=./builtin/providers/aws TESTARGS='-run=AWSLaunchConfiguration' 2>/dev/null

go generate ./...
TF_ACC=1 go test ./builtin/providers/aws -v -run=AWSLaunchConfiguration -timeout 90m
=== RUN TestAccAWSLaunchConfiguration_basic
--- PASS: TestAccAWSLaunchConfiguration_basic (2.60s)
=== RUN TestAccAWSLaunchConfiguration_withBlockDevices
--- PASS: TestAccAWSLaunchConfiguration_withBlockDevices (3.98s)
=== RUN TestAccAWSLaunchConfiguration_withSpotPrice
--- PASS: TestAccAWSLaunchConfiguration_withSpotPrice (1.92s)
PASS
ok      github.com/hashicorp/terraform/builtin/providers/aws    8.516s

cc @bantonj @frntn

[mitchellh]

LGTM, merge at will.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.