Rename aws_db_instance.subnet_group_name to db_subnet_group_name

Makes us consistent with RDS API and CLI tools, and is unambiguous: in AWS, there are a couple different kinds of "subnet group".

No backwards compatibilty concerns, since the new `subnet_group_name` attribute wasn't released in 0.2.2.