ref(eslint): enable no-unsafe-arguments in scraps

[TkDodo]

No description provided.

[TkDodo]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 66fd55b. Configure here.}

[github-actions]

📊 Type Coverage Diff

Metric	Before	After	Delta
Coverage	93.56%	93.57%	🟢 +0.01%
Typed	135,613	135,625	🟢 +12
Untyped	9,336	9,325	🟢 -11

🔍 6 new type safety issues introduced

Type assertions (as) (6 new)

File	Line	Detail
static/app/components/core/layout/container.tsx	257	`as keyof ContainerLayoutProps
static/app/components/core/layout/flex.tsx	67	`as keyof FlexLayoutProps
static/app/components/core/layout/grid.tsx	100	`as keyof GridLayoutProps
static/app/components/core/segmentedControl/segmentedControl.tsx	108	as Parameters<typeof useCollection>[0] — props as Parameters<typeof useCollection>[0]
static/app/components/core/separator/separator.tsx	24	as keyof SeparatorProps — prop as keyof SeparatorProps
static/app/components/teamSelector.tsx	196	`as unknown[]

This is informational only and does not block the PR.

[priscilawebdev]

instead of adding eslint comments here, what if we update the compare function?

  const compare = (a: unknown, b: unknown) => {
    if (props.isValueEqual && defined(a) && defined(b)) {
      return props.isValueEqual(
        a as OptionType['value'],
        b as OptionType['value'],
      );
    }
    return a === b;
  };

[TkDodo]

the problem is that opt.value is of type any because of some underlying types in react-select we can’t change :/ The eslint comment surfaces this, I think changing the input types to unkonwn with a type assertion might just lead to wrong things being passed in

[priscilawebdev]

left 1 suggestion, but it looks good to me