Pedantic eslint complaints

Got some messages from eslint. Maybe you can adjust for the empty objects we love in Rust.

Code:

export type ExecuteMsg =
  | {
      bond: {};
    }
  | ...

Error message:

  19:11  error  Don't use `{}` as a type. `{}` actually means "any non-nullish value".
- If you want a type meaning "any object", you probably want `Record<string, unknown>` instead.
- If you want a type meaning "any value", you probably want `unknown` instead.
- If you want a type meaning "empty object", you probably want `Record<string, never>` instead  @typescript-eslint/ban-types

I just manually updated mine to Record<string, never>

Start by locating the TypeScript code-generation path that emits the ExecuteMsg empty-object variants and run the relevant lint checks. Replace generated empty-object types with the intended empty-object representation, then confirm the generated output no longer triggers @typescript-eslint/ban-types.