chore: fix and format using melos

packages/wyatt_bloc_helper/lib/src/mixins/bloc_base_provider_mixin.dart

@@ -25,7 +25,7 @@ mixin BlocBaseProviderMixin<Bloc extends BlocBase<Object>> {
 
   /// Returns another [BlocBase] **not** used by this [BlocBaseProviderMixin].
   /// Short hand for `context.read<AnotherBloc>();`
-  /// 
+  ///
   /// To get [BlocBase] used by by this [BlocBaseProviderMixin] see `bloc()`
   AnotherBloc anotherBloc<AnotherBloc>(BuildContext context) =>
       context.read<AnotherBloc>();

packages/wyatt_bloc_helper/lib/src/mixins/bloc_provider_mixin.dart

@@ -21,7 +21,7 @@ import 'package:flutter_bloc/flutter_bloc.dart' as blocbase;
 /// of helper methods for events.
 mixin BlocProviderMixin<Bloc extends blocbase.Bloc<Event, Object>, Event> {
   /// Add an event to the [Bloc].
-  /// 
+  ///
   /// Short hand for `context.read<Bloc>().add(event)`.
   void add(BuildContext context, Event event) =>
       context.read<Bloc>().add(event);

packages/wyatt_bloc_helper/lib/src/widgets/multi_provider.dart

@@ -18,14 +18,14 @@ import 'package:flutter/widgets.dart';
 import 'package:flutter_bloc/flutter_bloc.dart';
 
 /// {@template multi_provider}
-/// Merges [MultiRepositoryProvider] and [MultiBlocProvider] widgets into 
+/// Merges [MultiRepositoryProvider] and [MultiBlocProvider] widgets into
 /// one widget tree.
 ///
 /// [MultiProvider] improves the readability and eliminates the need
 /// to nest multiple providers.
 ///
 /// By using [MultiProvider] we can go from:
-/// 
+///
 /// ```dart
 /// MultiRepositoryProvider(
 ///   providers: [
@@ -69,7 +69,7 @@ import 'package:flutter_bloc/flutter_bloc.dart';
 /// )
 /// ```
 ///
-/// [MultiProvider] converts the [RepositoryProvider] and [BlocProvider] lists 
+/// [MultiProvider] converts the [RepositoryProvider] and [BlocProvider] lists
 /// into a tree of nested provider widgets.
 /// As a result, the only advantage of using [MultiProvider] is
 /// improved readability due to the reduction in nesting and boilerplate.