Fix export of clone utility.

[Aaronius]

Description

We're using ES5 to import modules so we have to use ES5 to export the modules (you don't have to, but the process to import the module is a little more involved). In this case, I did an ES6 export default, resulting an error being thrown at runtime. This PR switches it to an ES5 export. I've logged a separate issue to add a lint rule so we can catch this type of thing earlier: https://jira.corp.adobe.com/browse/CORE-54412

Related Issue

It doesn't resolve this issue, but it is related: https://jira.corp.adobe.com/browse/CORE-54412

Motivation and Context

The send event action was throwing an error.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• All tests pass and I've made any necessary test changes.
• I've updated the schema in extension.json or no changes are necessary.

[ninaceban]

👍 Thank you!