Feat: Add automerge github shared workflow

[vaibhav7797]

what

• Describe high-level what changed as a result of these commits (i.e. in plain-english, what do these changes mean?)
• Use bullet points to be concise and to the point.

why

• Provide the justifications for the changes (e.g. business case).
• Describe why these changes were made (e.g. why do these commits fix the problem?)
• Use bullet points to be concise and to the point.

references

• Link to any supporting jira issues or helpful documentation to add some context (e.g. stackoverflow).
• Use closes #123, if this PR closes a Jira issue #123

[clouddrove-ci]

Terraform Security Scan Failed

Show Output

Result #1 LOW Log group is not encrypted. 
────────────────────────────────────────────────────────────────────────────────
  main.tf:49-52
────────────────────────────────────────────────────────────────────────────────
   49    resource "aws_cloudwatch_log_group" "sftp_log_group" {
   50      name              = "/aws/transfer/${module.labels.id}"
   51      retention_in_days = 90
   52    }
────────────────────────────────────────────────────────────────────────────────
          ID aws-cloudwatch-log-group-customer-key
      Impact Log data may be leaked if the logs are compromised. No auditing of who have viewed the logs.
  Resolution Enable CMK encryption of CloudWatch Log Groups

  More Information
  - https://aquasecurity.github.io/tfsec/latest/checks/aws/cloudwatch/log-group-customer-key/
  - https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/cloudwatch_log_group#kms_key_id
────────────────────────────────────────────────────────────────────────────────


  timings
  ──────────────────────────────────────────
  disk i/o             100.637µs
  parsing              61.456063ms
  adaptation           126.215µs
  checks               5.331976ms
  total                67.014891ms

  counts
  ──────────────────────────────────────────
  modules downloaded   0
  modules processed    1
  blocks processed     46
  files read           4

  results
  ──────────────────────────────────────────
  passed               0
  ignored              0
  critical             0
  high                 0
  medium               0
  low                  1

  1 potential problem(s) detected.