Use typed RefactoringOptions in the Dart version of the protocol.

pkg/analysis_server/test/integration/integration_test_methods.dart

 // Copyright (c) 2014, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 //
 // This file has been automatically generated.  Please do not edit it manually.
 // To regenerate the file, use the script
 // "pkg/analysis_server/spec/generate_files".
 
 /**
  * Convenience methods for running integration tests
@@ skipping 1109 matching lines @@
    *
    * length ( int )
    *
    *   The length of the region involved in the refactoring.
    *
    * validateOnly ( bool )
    *
    *   True if the client is only requesting that the values of the options be
    *   validated and no change be generated.
    *
-   * options ( optional object )
+   * options ( optional RefactoringOptions )
    *
    *   Data used to provide values provided by the user. The structure of the
    *   data is dependent on the kind of refactoring being performed. The data
    *   that is expected is documented in the section titled Refactorings,
    *   labeled as “Options”. This field can be omitted if the refactoring does
    *   not require any options or if the values of those options are not known.
    *
    * Returns
    *
    * problems ( List<RefactoringProblem> )
@@ skipping 317 matching lines @@
       case "debug.launchData":
         expect(params, isDebugLaunchDataParams);
         _onDebugLaunchData.add(params);
         break;
       default:
         fail('Unexpected notification: $event');
         break;
     }
   }
 }