feat: modal implementation for data ingestion table

[soleksy-splunk]

Issue number: ADDON-70993, ADDON-72969

Summary

Changes

Added a modal for data ingestion table view to show the specific data for input selector.

User experience

Users can see the data volume and number of events visualization chart for the particular row using the modal popup in data ingestion table.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

[soleksy-splunk]

@rohanm-crest as there was data_ingestion_modal_definition.json created, there is also a need to adjust smoke tests accordingly
so to file tests/testdata/expected_addons/expected_files_conflict_test/expected_log.json
at the end you need to add

  "appserver/static/js/build/custom/resources_tab_definition.json                  created\u001b[0m": "INFO",
  "appserver/static/js/build/custom/data_ingestion_modal_definition.json           created\u001b[0m": "INFO"

instead of current

  "appserver/static/js/build/custom/resources_tab_definition.json                  created\u001b[0m": "INFO"

lets make sure pipelines passed and i will than check all of it

[soleksy-splunk]

just a small thing i found after brief look

[soleksy-splunk]

some ideas regarding selector inside modal,

1. selector with input shouldn't be a part of fetched JSON, as data for it we can get inside method handleDashboardEvent via events

targetId: "data_ingestion_table_ds"
type: "datasource.done"

inside payload there are all data from table, thanks to that we can have all inputs from first column and add it into selector,

Also it would be nice to have a separated selector (from definition.json) as we need to change json definition based on selector change) , if user clicks testInput2 we need to adjust search queries,
Similar mechanism is already done for search functionality

2. We can always use as it is so keep selector input inside definition.json but
   cons:
   we will double number of search calls (maybe not issue as they are cached)
   we need to find a way to dynamically edit search query based on those changes

pros:
less flickering
everything from ui perspective is handled via dashboard components

[soleksy-splunk]

Also lets remember to not marge it untill we align all dynamics part into this PR.

[soleksy-splunk]

unfortunately seems like number of events diagram does not work correctly

here is a view even when it works for rest

I got all data by creating addon like that

ucc-gen init --addon-name "demo_addon_for_splunk” —addon-display-name "Demo Add-on for Splunk" --addon-input-name demo_input

poetry install
cd ui && sudo yarn run setup
cd ..
cp -n -R ui/dist/build/ splunk_add_on_ucc_framework/package/appserver/static/js/build/

poetry run ucc-gen build --source demo_addon_for_splunk/package

poetry run ucc-gen package --path output/demo_addon_for_splunk

after that just fill accounts in configuration page and add some inputs inside inputs page, wait 1-5 min and you should have all diagrams

[soleksy-splunk]

Some comments left

Also a question can we render dashboard components faster, as currently i believe we display dashboard panels after we get all data for drop down, but we should be displaying all at once and if anything goes wrong just hide drop down with inputs

[soleksy-splunk]

all looks good except that line
https://github.com/splunk/addonfactory-ucc-generator/pull/1244/files#diff-1eb337cab3b2550b4dec3115308f2f424bf6fb4c614683016fa667efc5a6e734R20

seems like when we remove it we have errors that shouldn't occur, but due to i wasn't a ble to reproduce it on real environment and that PR is here for long time i would say lets merge it and fix that one in next branch