As a swatch developer, I'd like to remove logic for force syncing an org's subscriptions when looking up billing identifiers.

This logic is unneeded given we process subscription updates via UMB messages.

FYI: This was originally in the lookupAwsUsageContext and lookupRhmUsageContext methods. 

Done

• swatch-producer-red-hat-marketplace does not force a subscription sync when looking up an orgs billing identifiers and no record exists swatch-contract 
• swatch-producer-aws does not force a subscription sync when looking up an orgs billing identifiers and no record exists swatch-contract 
• A warning is logged for the usage that is unable to be sent to the marketplace. This warning should include all information needed to debug the problem. This includes
  • An machine readable ID for the log message to make log querying/reporting easier
  • Org affected
  • Product for which we can't send usage
  • Marketplace identifiers that we do have
  • Marketplace Usage metric affected (if we have one)
  • The amount of usage that couldn't be sent. 
• Other usage is still processed. 

QE:

Verify no subscription syncing on hourly tally trigger. Verify warning message for usage unable to sent to marketplace and create splunk alert.