Add RBR reason to LHN debugging

[puneetlath]

As discussed here, let's add the reason a given report is showing an RBR in the LHN to the reports debug information. Similar to what we do for GBRs.

cc @pac-guerreiro

[melvin-bot[bot]]

Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new.

[melvin-bot[bot]]

:warning: It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time :warning:

[melvin-bot[bot]]

Triggered auto assignment to Design team member for new feature review - @dubielzyk-expensify (NewFeature)

[pac-guerreiro]

Hi! I’m Pedro Guerreiro from Callstack - expert contributor group. I’d like to work on this task!

[pac-guerreiro]

Hey, yesterday I opened a draft PR for this so you can see my progress while I work on this issue 😄

Here is what remains to be done:

• [ ] Add RBR reason test cases in DebugUtilsTest.ts
• [ ] Add screenshots
• [ ] Add QA testing steps

[pac-guerreiro]

Today's update:

• [x] Add RBR reason test cases in DebugUtilsTest.ts

Todo:

• [ ] Fix unit test for when there are transaction thread violations
• [ ] Add screenshots
• [ ] Add QA testing steps

[puneetlath]

Thanks for these updates!

[pac-guerreiro]

The PR is now ready for review! 😄

Go ahead @DylanDylann

[pac-guerreiro]

I just applied the suggested changes by @puneetlath and @DylanDylann.

The PR is ready for a new review 😄