Update to 2 biggest-near neighbors rather than 1 big 1 nearest.

This is the actual parameters of the model that is checked in, rather
than the current 1/1. I.e. there's a bug in submitted code that shows
when executing. Apologies.

Bug: 1009290
Change-Id: I3bcbe8eed8a81cb6979029f5f52f350b50c2e765
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1913683
Auto-Submit: Rob Schonberger <robsc@chromium.org>
Reviewed-by: Sean O'Brien <seobrien@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Rob Schonberger <robsc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#715107}

ui/events/ozone/evdev/touch_filter/palm_model/onedevice_train_palm_detection_filter_model.cc

@@ -48,8 +48,8 @@ OneDeviceTrainNeuralStylusPalmDetectionFilterModel::config() const {
 
 OneDeviceTrainNeuralStylusPalmDetectionFilterModel::
     OneDeviceTrainNeuralStylusPalmDetectionFilterModel() {
-  config_.nearest_neighbor_count = 1;
-  config_.biggest_near_neighbor_count = 1;
+  config_.nearest_neighbor_count = 0;
+  config_.biggest_near_neighbor_count = 2;
   config_.include_sequence_count_in_strokes = true;
   config_.max_neighbor_distance_in_mm = 100.0f;
   config_.min_sample_count = 6;