Fix previously uncaught violations of invalid override method parameter default values.

More correct checking of invalid override method parameter default values recently landed in the SDK [1]. The changes fit a few shapes, given a method `m1`, which overrides a method `m2`:

* If `m2` has a parameter `p` with a default value, but the parameter `p` on
  `m1` does _not_ have a default value, I have added a default value.
* If `m2` has a parameter `p` with a default value, and the parameter `p` on
  `m1` has a _different_ default value, I have either:
  * changed the default value on `m1` to equal that on `m2`, or
  * removed the default value on `m2`, instead assigning it with `??=` as the
    first statement in the method body.

[1] dart-lang/sdk#34437

PiperOrigin-RevId: 233486440

Author: keertip

angular_components/lib/model/selection/select.dart

@@ -42,7 +42,7 @@ abstract class Filterable {
   /// filter('re', limit: 5) for return colors whose names start with 're'
   /// filter(new DateTime.now(), limit: 10) for showing only meeting that are in
   /// the future.
-  DisposableFuture<bool> filter(Object filterQuery, {int limit = -1});
+  DisposableFuture<bool> filter(Object filterQuery, {int limit});
 }
 
 /// Interface implemented by classes that support children.