Use any for untyped Object/Function in flow-typed and debugger-shell

Summary:
With `experimental.function_and_object_type_is_no_longer_any`, Flow resolves `Object` and `Function` to the builtin class types instead of `any`. These annotations relied on the old meaning, so they become `any`:
- `cli-types`: the `CommandFunction<Object>` of `Command.func`. Commands with exact arg types no longer fit it.
- `yargs`: the `command` handler, which gave handlers an `any` context. `js1 fox` handlers rely on it.
- `debugger-shell`: `SettingsStore`'s default values, which are read by key.

Changelog: [Internal]

Differential Revision: D125303674

Author: SamChou19815

flow-typed/npm/@react-native-community/cli-types_v19.x.x.js

@@ -35,7 +35,7 @@ declare module '@react-native-community/cli-types' {
       name: string,
       version: string,
     },
-    func: CommandFunction<Object>,
+    func: CommandFunction<any>,
     options?: Array<CommandOption<(ctx: Config) => OptionValue>>,
   };
 

flow-typed/npm/yargs_v17.x.x.js

@@ -103,7 +103,7 @@ declare module 'yargs' {
       builder?:
         | {[key: string]: Options, ...}
         | ((yargsInstance: Yargs) => unknown),
-      handler?: Function,
+      handler?: any,
     ): this;
     command(
       cmd: string | Array<string>,

packages/debugger-shell/src/electron/SettingsStore.js

@@ -30,7 +30,7 @@ type Options = Readonly<{
  * - Supports the Electron main process only.
  */
 export default class SettingsStore {
-  #defaultValues: Object = {};
+  #defaultValues: any = {};
   path: string;
 
   constructor(options: Options = {}) {