Fixed handling of reason on unbonding events

[Alann27]

Summary

Fixed handling of reason on unbonding events for Applications and Suppliers

Issue

The variable reason was of type number, receiving its value from an enum (i.e., by calling applicationUnbondingReasonFromJSON). We were incorrectly throwing an error when reason was falsy (!reason). This caused an issue when reason was the first item in the enum (with a value of 0), as 0 is a valid value but was mistakenly treated as an error.

Type of change

Select one or more:

• New feature, functionality or library
• Bug fix
• Code health or cleanup
• Documentation
• Other (specify)

Sanity Checklist

• I have tested my changes using the available tooling
• I have commented my code
• I have performed a self-review of my own code; both comments & source code
• I create and reference any new tickets, if applicable
• I have left TODOs throughout the codebase, if applicable