Feature: Show Connection-Status, Show Agent Attributes, Filter By Properties and Attributes

[levinkerschberger]

Luckily everything in /shadcn/ can be ignored, so it´s not that much code...

[EddeCCC]

LGTM

Some things that I noticed:

• In the "Service Name" filter, I can only select "All" or services with connection status CONNECTED
• The default value for the "Connection Status" filter is CONNECTED, could you change this to "All"
• It appears weird to me, that the root page leads directly to the connections. Could you add the path /connections also in the UI? So I can access the page e.g. via localhost:8080/connections

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
No data about Coverage
1.0% Duplication on New Code

See analysis details on SonarQube Cloud

[levinkerschberger]

Thanks for the review @EddeCCC,

"In the "Service Name" filter, I can only select "All" or services with connection status CONNECTED"
there was indeed a Bug.

The memo "uniqueFilterValues" did not get updated, so basically the inital filterstate in ConnectionTable.tsx controlled the selection options. Now it works as expected.

Also the Filter-Function, SonarQube wanted made issues, cause "Attributes"-Column is a little more complex then just a String.
Removed the sorting for any non-trivial Filters

"The default value for the "Connection Status" filter is CONNECTED"

That was with purpose. Ingrida wanted it like that.

"It appears weird to me, that the root page leads directly to the connections. Could you add the path /connections also in the UI? So I can access the page e.g. via localhost:8080/connections"

You can also access the page via localhost:8080/connections. Also when you click onto the menu point "Connections" you´ll get redirected to /connections. The ConnectionsPage-Component is routed onto both routes ("/" and "/connections"). I think that is valid, cause I don´t know what else to put onto the main-route... Maybe a Dashboard in the future?
An instand redirect to /connection is also not really intuitive and quite weird to implement with react-router v6.