Fix navigation crash

[vargaat]

What happened?

• There were two crashes related to a navigation controller being pushed into another navigation controller.
• One crash was because of interactions between UIPrint* classes and based on the crash logs they no longer appear on iOS 18 so most probably this is an iOS level bug that got fixed.
• The other variant was most probably from our code but I couldn't reproduce the error not even based on the routes the user visited.
• To avoid such crashes I added a safeguard not to allow our nav controller to push another nav controller.
• I refactored our error / breadcrumb reporting to Crashlytics. My main concern there was that developer related log and error functions were mixed with the regular usage statistics methods and it was hard to understand what goes to which service. I separated developer related debug helping reporting methods into a dedicated entity to make things more easy. There are many code changes but most of them just about moving code around and renaming.
• I also changed when a new route is reported as a breadcrumb. Previously it was after presentation and in case the presentation crashed we lost the log. Now the route is logged before the actual routing takes place.

Checklist

• Tested on phone
• Tested on tablet

[inst-danger]

	Warnings
⚠️	This pull request will not generate a release note.
⚠️	One or more files are below the minimum test coverage 50%

Affected Apps: Student, Teacher, Parent

MBL-18060

Coverage	New %	Master %	Delta
Canvas iOS	91.42%	91.43%	-0.01%
Core/Core/Assignments/AssignmentList/ViewModel/AssignmentListViewModel.swift	47.8%	47.8%	0%

Generated by 🚫 dangerJS against d699dde

[suhaibabsi-inst]

Thanks @vargaat !

Code +1

P.S. I was not able to test this on Firebase for lack of permission to DebugView.
Will be working on fixing that issue.