specify grpc as appprotocol in cfn exmaple, needed to properly export traces

[sMailund]

… traces

Description

During our integration with Coralogix, we were only able to logs, but not able to export traces.

In a call with a Coralogix representative, we were shown example code where the only difference was that appProtocol was specified. It turned out we had copied the example code from this cloudformation template, which didn't specify grpc as appProtocol. After reploying with appprotocol specified, traces started showing up in our Coralogix console.

How Has This Been Tested?

Solved the issue in our case. I would assume other integrators using the same setup with a sidecar in ECS will also need to specify grpc the same way. Feel free to reject this PR if that is not the case!

Checklist:

• I have updated the relevant component changelog(s)
• This change does not affect any particular component (e.g. it's readme or docs change)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Simen Mailund Svendsen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[MichaelBriggs-Coralogix]

Thank you for your contribution to the repo! Please do adjust the http protocol in your commit and submit your signature on the Contributor License Agreement.

[sMailund]

Updated and signed CLA. For the record, it turned out this was not actually what fixed our issue, but it still helps to properly specify the appProtocol hopefully!

[MichaelBriggs-Coralogix]

Looks good.

[MichaelBriggs-Coralogix]

@sMailund Would you be able to resubmit your commits after setting up user signing? Commits need to be signed in order to be merged.