Fix sending tags when rejecting the push permission prompt

[emawby]

Description

One Line Summary

Checking for a playerId before trying to sendTagsOnBackground

Details

When the push prompt is displayed the application background lifecycle method is called. This results in trying to sendTagsOnBackground but we may not have a playerId yet. This adds a check for playerId so that we don't erroneously try to send tags without a playerId

Motivation

This PR fixes a customer reported issue regarding sending tags when the push prompt is declined

Testing

Manual testing

I have tested on multiple example apps on my iPhone

Affected code checklist

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

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 

[nan-li]

How do the tags end up being sent for users who decline push permission?

[emawby]

How do the tags end up being sent for users who decline push permission?

Previously we were trying to send the tag before the user responded to the prompt and it wouldn't try to send it when the player is created. Now it won't try to send it before the user responds to the prompt so the tags will be sent when the player is created after the prompt is responded to. We create the player regardless of the whether or not the user accepts or denies the prompt

[jkasten2]

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