feat: adds support to \n separated request body for ga forwarding

[kevinpagtakhan]

Summary

When this feature was originally built, GA sent bulk events in a single request using the request payload. The request payload is a list of valid query parameter formatted string separated by the \\r\\ character. A customer reported that their GA-forwarded events are not being formatted correctly. After some investigating, we are seeing the list of valid query parameter formatted stings are separated by \n character. The changes here include adding support to \n separated strings and ignoring events that are formatted outside the supported formats.

Checklist

• Does your PR title have the correct title format?
• Does your PR have a breaking change?: No

[Mercy811]

Thanks Kevin for adding this. Overall looks good to me. See the comment about the change to user id.