refactor: DH-19267: columns changed filter event takes an id rather than a panel

[dgodinez-dh]

https://deephaven.atlassian.net/browse/DH-19267

Refactors InputFilterEvent.COLUMNS_CHANGED to take an id instead of a panel. This can be a panel id or a widget id. This will allow deephaven.ui components to send this event. Note that more work will need to be done on Linker. This will be done later when we address https://deephaven.atlassian.net/browse/DH-18840

[codecov]

Codecov Report

Attention: Patch coverage is 31.57895% with 13 lines in your changes missing coverage. Please review.

Project coverage is 46.92%. Comparing base (2827f51) to head (1e51672).

Files with missing lines	Patch %	Lines
...ckages/dashboard-core-plugins/src/FilterPlugin.tsx	22.22%	7 Missing ⚠️
...kages/dashboard-core-plugins/src/linker/Linker.tsx	0.00%	6 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #2417    +/-   ##
========================================
  Coverage   46.92%   46.92%            
========================================
  Files         712      712            
  Lines       39341    39343     +2     
  Branches    10024     9836   -188     
========================================
+ Hits        18462    18463     +1     
- Misses      20868    20869     +1     
  Partials       11       11            

Flag	Coverage Δ
unit	46.92% <31.57%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[bmingles]

In case you haven't seen it, we now have a Brand type (packages/utils/src/TypeUtils.ts). It's useful for ensuring things like Ids don't get assigned to the wrong a field expecting a different id type. Usage is:

type WidgetId = Brand<'WidgetId'> // 2nd generic defaults to string

or

type WidgetId = Brand<'WidgetId', string>
...

// creation
const id = 'someId' as WidgetId

That said, it does require some type assertions in certain cases when creating ids, so there are tradeoffs. Can also sometimes create a rabbit hole when converting a type that is already in use in a lot of places. Just wanted to call it out in case it is a good fit here.

[dgodinez-dh]

Updated

[bmingles]

Same suggestion here to consider the Brand type.

Suggested change

	export type PanelId = string | string[] | null | undefined;
	export type PanelId = Brand<'PanelId', string | string[] | null | undefined>;

[dgodinez-dh]

Updated

[bmingles]

Left suggestions for using Brand type helper.

[bmingles]

LGTM