509 evss backend sentry error to info

[LindseySaari]

Description of change

This change reduces Sentry noise by logging the EVSSBackendServiceError with a level of info instead of error, no longer creating a sentry error alert. After discussion, triggering a sentry alert is not necessary.

Testing done

Spec tests run & pass
Sentry logging remains the same for other error logging

Acceptance Criteria (Definition of Done)

• Spec tests passing
• Sentry alerts are no longer recording EVSSBackendServiceError with a level of error
• The EVSSBackendServiceError is an info-level event

Applies to all PRs

• Appropriate logging
• Swagger docs have been updated, if applicable
• Provide link to originating GitHub issue, or connected to it via ZenHub
• Does not contain any sensitive information (i.e. PII/credentials/internal URLs/etc., in logging, hardcoded, or in specs)
• Provide which alerts would indicate a problem with this functionality (if applicable)

[jholton]

I missed the first PR that this one builds off of. I would have said this then:

I think should move logic that changes an error's 'level' into a Sentry processor. We already have one that sets certain exceptions to :warn. Now we have multiple places where 'levels' are set.

We should keep this type of logic in one place (processors, IMO). Otherwise we are asking for a situation in the future where sentry_logging sets a level and then a processor sets it to something else.

[kfrz]

Think this might live better in EVSS middleware.

[kfrz]

@jholton just FYI - we are going to merge this change for now to supress the particular EVSS 503 response, but we will be working to refactor our overall error handling in order to leverage a sentry processor/middleware pattern.

[kfrz]

Let's merge this for now!