feat(in-app-messaging): update InAppMessagingDisplay and useInAppMessage

[calebpollman]

Description of changes

Follow up to PR #9026.

• add additional logging and try/catch blocks in handleAction
• add optional chaining on content values to prevent accessing falsy values in useInAppMessage
• add optional chaining to call of onActionCallback in onPress passed to buttons
• handle falsy values and prevent assigning empty values in getContentProps
• migrate to default and explicit exports in in-app messaging feature code

Issue #, if available

NA

Description of how you validated changes

Manually tested in sample app

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[codecov-commenter]

Codecov Report

Merging #9088 (fe38553) into in-app-messaging/main (f5ff575) will not change coverage.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##           in-app-messaging/main    #9088   +/-   ##
======================================================
  Coverage                  78.00%   78.00%           
======================================================
  Files                        250      250           
  Lines                      18115    18115           
  Branches                    3885     3885           
======================================================
  Hits                       14131    14131           
  Misses                      3854     3854           
  Partials                     130      130           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f5ff575...fe38553. Read the comment docs.

[elorzafe]

LGTM 🌮

[nickarocho]

Looks good! Thanks, Caleb 🚢

[github-actions]

This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels or Discussions for those types of questions.