Add cancel button to preview UI

[koszti]

Description

Add Preempt and Kill control buttons to the preview query overview header.

Screenshots:

..

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
(x) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Add kill and preempt buttons to preview UII. ({issue}`29315`)

[mosabua]

@sajjoseph can you also test this ?

[mosabua]

Overall pretty much good to go .. just some minor things to figure out.

[mosabua]

Also one more thought .. in case I understand this correctly..

Preempt only applies to queries that are not yet running
Kill only applies to queries that are already running

So could we not just have one button that says "Stop processing" or something .. and it does the right thing depending on the the query?

[RoeyoOgen]

Also one more thought .. in case I understand this correctly..

Preempt only applies to queries that are not yet running

Kill only applies to queries that are already running

So could we not just have one button that says "Stop processing" or something .. and it does the right thing depending on the the query?

Agree, makes sense

[koszti]

@mosabua @RoeyoOgen , I looked through the backend java code and I think the only difference between kill and preempt is the message. Both paths call the same failQuery method, just with different exception messages: UiQueryResource.java#131

Given that I combined the two actions into a single Cancel query button, using the message Canceled via web UI.

let me know your thoughts.

...

[sajjoseph]

I like the cancel query approach to combine the actions.

[mosabua]

Just fyi @koszti .. I rebased and pushed to test and potentially merge

[mosabua]

@koszti I am getting build failures locally .. can you check?

[INFO] src/components/QueryOverview.tsx(519,37): error TS2769: No overload matches this call.
[INFO]   Overload 1 of 3, '(props: { href: string; } & ButtonOwnProps & Omit<ButtonBaseOwnProps, "classes"> & CommonProps & Omit<DetailedHTMLProps<AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement>, "children" | ... 27 more ... | "startIcon">): Element', gave the following error.
[INFO]     Type 'string | true | null' is not assignable to type 'boolean | undefined'.
[INFO]       Type 'null' is not assignable to type 'boolean | undefined'.
[INFO]   Overload 2 of 3, '(props: { component: ElementType<any, keyof IntrinsicElements>; } & ButtonOwnProps & Omit<ButtonBaseOwnProps, "classes"> & CommonProps & Omit<...>): Element | null', gave the following error.
[INFO]     Type 'string | true | null' is not assignable to type 'boolean | undefined'.
[INFO]       Type 'null' is not assignable to type 'boolean | undefined'.
[INFO]   Overload 3 of 3, '(props: DefaultComponentProps<ExtendButtonBaseTypeMap<ButtonTypeMap<{}, "button">>>): Element | null', gave the following error.
[INFO]     Type 'string | true | null' is not assignable to type 'boolean | undefined'.
[INFO]       Type 'null' is not assignable to type 'boolean | undefined'.
[INFO]

[koszti]

@mosabua I fixed the tests, everything is green now

[mosabua]

Looks good now. Thank you @koszti

[koszti]

@mosabua do you know why this PR removed from the merge queue? It says build-success is failed (https://github.com/trinodb/trino/actions/runs/25678587154/job/75388409099), but all CI checks passed. Am I missing something?

[mosabua]

The queue is weird .. if it fails even an unrelated test it gets bumped off it seems .. I put it back on the queue

[ebyhr]

## Section
* Add kill and preempt buttons to preview UII. ({issue}`29315`)

The section should be Web UI and there is a typo > UII.