UI for `POST v1/evc/check_consistency`

[viniarck]

This is for implementing a UI for POST v1/evc/check_consistency that was implemented on #173.

• OpenAPI docs

Network Operator Use Case

• The UI should provide a quick way to run and easily identify inconsistent INT EVCs. An inconsistent EVC is an EVC with its outcome: "inconsistent" which implies that it either has extra (alien) or missing flows.
• The UI should also display nicely for each EVC if any flows are missing, which ones, and if there are flows which ones, the view should be handy to try to understand what's going on

Requirements

• The UI should provide a way to select a set of EVCs or run on all of them
• The UI should support all query args of this endpoint
• When a user wants to also set the argument inconsistent_action=fix|redeploy|disable which might perform a side effect if there are inconsistent EVC it should use a modal to confirm to avoid surprises

Ideas

• Maybe we could reuse show_telemetry_int_data.kytos for selection, and augment the option to run consistency check with a new button and expose the related configs and then display in a new k-info-panel? If we end up reusing this we can't allow network operators to get confused the consistency options with enable/disable options
• Maybe we also could use a 3 column table for each EVC displaying the expected flows, missing flows and alien flows, just so they can view a sort of way "3-way" view for a quick analysis to understand what's going on

cc'ing @HeriLFIU for his information. Now it's too late for 2025.2, but it'll be nice to eventually have this UI implemented too Heriberto, and this will be a challenging one since the output can get lengthy we need a slick UI with scrolls and that provide a handy/quick information without clutter too much flow information. If you have any other ideas please augment here. Before implementing let's try to mock some visuals how this component will look like and get feedback from network operators. Please add this to your list, this will be on our top of our radar for upcoming tasks, thanks.

Check out the payload response examples I provided here for mocking data