fix(service-worker): don't crash if SW not supported

Currently a bug exists where attempting to inject SwPush crashes the
application if Service Workers are unsupported. This happens because
SwPush doesn't properly detect that navigator.serviceWorker isn't
set.

This change ensures that all passive observation of SwPush and
SwUpdate doesn't cause crashes, and that calling methods to perform
actions on them results in rejected Promises. It's up to applications
to detect when those services are not available, and refrain from
attempting to use them.

To that end, this change also adds an `isSupported` getter to both
services, so users don't have to rely on feature detection directly
with browser APIs. Currently this simply detects whether the SW API
is present, but in the future it will be expanded to detect whether
a particular browser supports specific APIs (such as push
notifications, for example).

tools/public_api_guard/service-worker/service-worker.d.ts

@@ -8,6 +8,7 @@ export declare class ServiceWorkerModule {
 
 /** @experimental */
 export declare class SwPush {
+    readonly isEnabled: boolean;
     readonly messages: Observable<object>;
     readonly subscription: Observable<PushSubscription | null>;
     constructor(sw: NgswCommChannel);
@@ -21,6 +22,7 @@ export declare class SwPush {
 export declare class SwUpdate {
     readonly activated: Observable<UpdateActivatedEvent>;
     readonly available: Observable<UpdateAvailableEvent>;
+    readonly isEnabled: boolean;
     constructor(sw: NgswCommChannel);
     activateUpdate(): Promise<void>;
     checkForUpdate(): Promise<void>;