Add debug, error logs for push notifications and update the service-worker's scope

[charleslavon]

This PR

• Adds debug and console error logs for improved debugging
• moves the push-notification worker into a new folder such that the default scope can be used, because there is frequent confusion surrounding the meaning and use of scope. Since a service worker can't have a scope broader than its own location, only use the scope option when you need a scope that is narrower than the default. (reference)

Areas for additional improvement

1. decouple the registering/de-registering of the push notification service worker from the UX flow of enabling/disabling push notifications. Instead, this worker can be added as an import script into the pwa service worker's config. The benefits would be easier local debugging of changes to push-notifications.js and would ensure that a user's browser would always refresh to the latest version of push-notifications.js without requiring them to disable and re-enable push notifications.
2. Push Notifications still are often not received by a client, even when notification data is properly traced through the backend flow and messages appear to be sent to the Apple/Google subscription endpoints. Right now we are essentially throwing into the ocean a message-in-a-bottle and hoping that it is received by the 3rd party subscription endpoint handler and then delivered to the user's client. We can find ways to improve this, perhaps by implementing support for read/delivery receipts or error logging.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
dev-near-org	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 18, 2024 3:32pm
near-discovery	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 18, 2024 3:32pm
near-discovery-testnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 18, 2024 3:32pm