Instead we're going to move back to standard exceptions.
Using a custom Result class has created far far more problems
- The Stacktraces aren't always right
- Sometimes one forgets to check the Result error
- All other exception throwing code needing to be converted to Results
- Non idiomatic Dart code
I think it's better to just go back to exceptions. They have their
problems, but overall, I think it's a better approach.
Even though I'm not using v4.2, the return-value rule is still being
applied with `flutter analyze` though not consistently.
For now, lets disable this, as there are 300+ warnings to fix.
