Fix calling setLaunchUrlsInApp after init

[emawby]

Description

One Line Summary

This allows setLaunchUrlsInApp to have an effect after init has been called

Details

launchURL behavior used to be a part of the init call in the previous major release. When the init call was split apart in the 3.0.0 major release the setLaunchUrlsInApp logic only worked if it was called prior to init because it set values in the appSettings dictionary instead of calling enableInAppLaunchUrls directly.

Testing

Manual testing

Tested setLaunchUrlsInApp true and false before and after init

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes
• Distribution

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is