fix: modify in-app event listener action parameters to new name

[levibostian]

Closes: https://github.com/customerio/issues/issues/9189

Docs already updated to reflect this change

[ami-oss-ci]

Pull request title looks good 👍!

If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.1. This pull request is not a breaking change.

All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.

To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy!

This pull request title should be in this format:

<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:

<type>!: short description of breaking change

where <type> is one of the following:

• feat: - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project.

• fix: - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project.

• docs: - This pull request is making documentation changes, only.

• refactor: - A change was made that doesn't fix a bug or add a feature.

• test: - Adds missing tests or fixes broken tests.

• style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

• perf: - Changes improve performance of the code.

• build: - Changes to the build system (maven, npm, gulp, etc)

• ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

• chore: - Other changes to project that don't modify source code or test files.

• revert: - Reverts a previous commit that was made.

Examples:

feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter 

Need more examples? Want to learn more about this format? Check out the official docs.

Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

[codecov]

Codecov Report

Merging #255 (8e2bd3b) into develop (acd12da) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff            @@
##           develop     #255   +/-   ##
========================================
  Coverage    56.11%   56.11%           
========================================
  Files          103      103           
  Lines         1153     1153           
========================================
  Hits           647      647           
  Misses         506      506           

Impacted Files	Coverage Δ
.../MessagingInApp/MessagingInAppImplementation.swift	78.57% <ø> (ø)
...ngInApp/autogenerated/AutoMockable.generated.swift	89.18% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[ami-oss-ci]

	Warnings
⚠️	I noticed file Tests/MessagingInApp/APITest.swift was modified. That could mean that this pull request is introducing a breaking change to the SDK. If this pull request does introduce a breaking change, make sure the pull request title is in the format: <type>!: description of breaking change // Example: refactor!: remove onComplete callback from async functions

Generated by 🚫 dangerJS against 8e2bd3b

[github-actions]

🎉 This PR is included in version 2.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀