Add groups and permissions for azure_devops_v1

[brk3]

This commit extends azure_devops_v1 to allow the user to create groups,
and assign these groups permissions to AZDO projects and pipelines
("build definitions").

The following example will:

1. Create a group in AZDO called "Contoso Group"
2. Added UPNs paul and john to this group
3. Assign this group full permissions on the project and builds.

groups = {
  contoso = {
    project_key  = "contoso_project"
    display_name = "Contoso Group"
    description  = "Group for Contoso Team Members"
    members = {
      user_principal_names = [
        "paul.bourke@contoso.com",
        "john.doe@contoso.com",
      ]
    }
  }
}

permissions = {
  projects = {
    contoso_project = {
      group_key = "contoso_project"
      permissions = {
        "GENERIC_READ"     = "Allow",
        "GENERIC_WRITE"    = "Allow",
        "START_BUILD"      = "Allow",
        "ADMINISTER_BUILD" = "Allow",
      }
    }
  }

  build_definitions = {
    end_to_end = {
      project_key = "contoso_project"
      group_key   = "contoso"
      permissions = {
        "ViewBuilds"          = "Allow",
        "QueueBuilds"         = "Allow",
        "ManageBuildQueue"    = "Allow",
        "StopBuilds"          = "Allow",
        "ViewBuildDefinition" = "Allow",
      }
    }

    rover_build = {
      project_key = "contoso_project"
      group_key   = "contoso"
      permissions = {
        "ViewBuilds"          = "Allow",
        "QueueBuilds"         = "Allow",
        "ManageBuildQueue"    = "Allow",
        "StopBuilds"          = "Allow",
        "ViewBuildDefinition" = "Allow",
      }
    }
  }
}

Issue-id

PR Checklist

---

• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran lint checks locally prior to submission.
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Description

Does this introduce a breaking change

• YES
• NO

Testing

[LaurentLesle]

Thanks @brk3 for those additions. LGTM