Handle errors gracefully for inactive subscriptions during seat links processing

Problem

Recently it has come to light that several inactive subscriptions(Ex: GCP logs) still attempt to post seat link data to customersDot. This was discovered from Sentry errors where an error log is generated for each unprocessible scenario.

Proposal

Soften the log from error to warn as the seat links creation modules do not generate seat links when either of these scenarios take place.