End background task after receiving location

[emawby]

Description

One Line Summary

OneSignal was kicking off a background task for requesting the location when the app entered the background, however we were not ending the background task after sending the location which caused an error log.

Fixes #1047

Details

When the app enters the background we kickoff a significant change location listener that does not require a background task to be active. If the significant change service is not available then we just ask for the current location and will not continue updating in the background. After we either kick off the significant change listener or receive the current location we need to end the background task.

Testing

Manual testing

I have successfully tested background location updating using the simulators mock location functionality. The error no longer appears and locations still are updated in the background.

Affected code checklist

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

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 

[jkasten2]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @nan-li)