Adds try/catch around notification failing with an inactive webhook for better user experience

[Godmartinz]

When checking in and checking out, if the webhook notification fires and there is an error, it now redirects back with an error message

[what-the-diff]

PR Summary

• Enhancement of Code Readability
  The code's formatting has been improved, making it easier to read. This was done by adding spaces around parentheses in conditionals.

• Upgraded Logging Mechanisms
  We've upgraded our logging techniques to be more suitable for error situations. Now we use Log::error rather than Log::debug.

• In-depth Error Report for Webhook Notifications
  New detailed error messages have been added to identify issues with webhook notification failures more easily. These messages include information such as the webhook endpoint and event details.

• Consistent Email Notifications
  We have refactored the process of sending out email notifications during check-outs and check-ins. This allows for consistent logging and error handling practices.

• Better Error Handling
  A more streamlined error handling practice has been introduced for webhook notifications, more specifically during the check-out and check-in stages.

[snipe]

Can we make this a warning or info? The red error makes it look like the checkout might not have worked, even though it did. I'd say if you're going to fire two error bags, make one "success" and then the next one an info - or combine them and make it a warning.

[snipe]

(I know what the messages say, but I also know what people will read.)

[marcusmoore]

Gave this a try and it worked. Code is good but I do recommend @snipe's suggestion of changing it to a warning.

[Godmartinz]

forgot to make it a translation--1 sec

[Godmartinz]

good 👍