ENHANCEMENT: Ability to set custom secret's name (have full control of the name) for AWS Secrets Manager

Currently when we use resource doppler_secrets_sync_aws_secrets_manager it will always add /doppler suffix in the end of the name.

For example:

resource "doppler_secrets_sync_aws_secrets_manager" "backend_prod" {
  integration = doppler_integration_aws_secrets_manager.prod.id
  project     = "backend"
  config      = "prd"

  region = "us-east-1"
  path   = "/backend/"
  tags   = { myTag = "enabled" }
}

this example will create secret backend/doppler on AWS side.

We would like to have full control over how the secret's name will be on AWS Secrets Manager, as we have naming convention for all (when is possible) AWS resources at our company. It will be great if we could achieve full compatibility when we get secrets via Doppler.

DopplerHQ / terraform-provider-doppler

ENHANCEMENT: Ability to set custom secret's name (have full control of the name) for AWS Secrets Manager #91