[Module Proposal]: `avm-res-communication-communicationservice`

### Check for previous/existing GitHub issues/module proposals

- [X] I have checked for previous/existing GitHub issues/module proposals.

### Check this module doesn't already exist in the module indexes

- [X] I have checked for that this module doesn't already exist in the module indexes.

### Bicep or Terraform?

Terraform

### Module Classification?

Resource Module

### Module Name

avm-res-communication-communicationservice

### Module Details

There is a Terraform module for the email communication service #1068, this is the parent communication resource.

This follows the pattern of Bicep where these are separate (#748 & #749)

### Do you want to be the owner of this module?

No

### Module Owner's GitHub Username (handle)

_No response_

### (Optional) Secondary Module Owner's GitHub Username (handle)

kewalaka

Start by reviewing the existing Terraform email communication service module proposal in #1068 and the related Bicep proposals in #748 and #749. Use those references to determine the parent communication resource's scope and module structure; done means a Terraform resource module named avm-res-communication-communicationservice that follows the repository's AVM standards.

Written by the indexing model from the issue text.