Add Provider Detail view with Yaml and Alerts

[joshri]

Closes #2566
Closes #2567
Closes #2568

• Providers in the NotificationsTable are now clickable links to the new ProviderPage page
• This page fetches the individual provider with useGetObject, and passes it down to the new ProviderDetail containing YamlView and AlertsTable tabs.
• The new AlertsTable takes the Alerts from an individual provider using the new useListAlerts as rows. This hook grabs all Alerts and filters them by providerRef to grab the correct ones for the table.
• Added Alert as an extension of FluxObject.
• Fixed a styling bug that's probably been in YamlView for a while - a 5px blank spot was reserved on the right side of the view, likely for a scrollbar. I removed horizontal scrolling on the view (it already pre-wraps), and extended the header all the way across.

The Events tab is impossible at the moment due to the flux notification-controller not recording kubernetes events. There is a remaining issue in the notification epic for a special display where no notifications are visible, and I believe that there were plans to add alert yaml on hover but I don't see an issue for it.

Clickable providers:

Alerts Table:

Provider yaml:

[ozamosi]

Could you please add ProviderDetail and NotificationsTable to index.ts too?

[ozamosi]

Should this not (also, I wrote more in the other comment) have a namespace?

[joshri]

This can definitely have namespace - how do you feel about:
{obj.kind}: {obj.name}, {obj.namespace}
Was it supposed to be namespace instead of name? Trying to follow the original design:

[ozamosi]

I think the comma could be confusing - looks a bit like it's doing some kind of {kind}: {objs.filter(o => o.kind == kind).map(o => o.name).join(', ')}.

I think I would do {obj.kind}: {obj.namespace}/{obj.name}

I almost said "because that's how it's usually displayed" and then I realised that it's not (if you run flux get all -A you get the {obj.kind}/{obj.name} in one column, and namespace in another one, and if you run kubectl port-forward --help then you'll see that you can also use {obj.kind}/{obj.name}) - but I can't think of anything better that's still somewhat faithful to the original design.

[opudrovs]

As I said, I see it for the Alerts table. If it's not a general filtering issue, it must be related to this PR:

[joshri]

It absolutely was related to this PR - good spot. Had the wrong value in the filterConfig function for event severity!! Fixed.

[opudrovs]

@joshri could you please rebase on main so that I could test search in the events table? Search is supposed to be working in this table, correct?