Feat: set volume_tags on aws_instance resource

[TomerHeber]

resolves #186

1. Added special handling for aws_instance resource.
2. Added an acceptance test for this use-case.

[TomerHeber]

Note: tests are failing due to an unrelated issue. (A bug in azure provider). This will probably be resolved very soon.

hashicorp/terraform-provider-azurerm#24749

[terenho-jobber]

This PR uses volume_tags in aws_instance https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#volume_tags, and it causes "root_block_device.0.tags": conflicts with volume_tags error with tags defined for the volumes.

To reproduce, the code below when run with Terraform in env0 would fail planning with "root_block_device.0.tags": conflicts with volume_tags

resource "aws_instance" "test_ec2" {
  ami                    = "ami-0f5daaa3a7fb3378b"
  instance_type          = "t2.micro"
  subnet_id              = "..."
  vpc_security_group_ids = [...]

  root_block_device {
    volume_size = 8
    tags = {
      Name = "test-ec2"
    }
  }
}