[w3c/push-api] Consider including `supportedContentEncodings` in the `PushSubscription` serializer (#277)

This came up in web-push-libs/web-push#278. Since we plan to deprecate "aesgcm" eventually, and `supportedContentEncodings` is the same for every subscription, including them in the serializer might not make sense...but it could be a nice convenience.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/277