feat: Add Discard Handling for AuthenticationError

[brunomiguelpinto]

Context:

In this pull request, we change the error handling within the StripeCreateJob by discarding jobs that encounter Stripe::AuthenticationError. This change ensures that we prevent creating noise

Description:

• When a Stripe::AuthenticationError is raised, it indicates an issue with the authentication credentials. Since this is a non-recoverable error in the job context, retries are unnecessary.
• Customers are already notified of such errors through a webhook, making additional retries redundant and potentially confusing for the customer.

Additional Context:

• The update_payment_method_id method in the related service sends a webhook notification when any Stripe::StripeError is raised, ensuring customers are informed of issues promptly.

[julienbourdeau]

TIL discard_on

I always rescued and ignore in perform. I like discard_on much better.

[vincent-pochet]

Some other errors are handled here:
https://github.com/getlago/lago-api/blob/main/app/services/invoices/payments/stripe_service.rb#L193

Not sure but I think we should do the same things here rather than just silencing the error.

• Optionally (since it seems already OK): Notifying the owner of the account that its stripe account is not correctly configured
• Setting the payment status to failed