Update NeXus search app in pynxtools

[GinzburgLev]

A generic app for search/statistics visualization for NXsensor_scan and inheriting classes (currently NXiv_temp, NXspm, NXstm, NXafm, NXsts); also will work for NOMAD CAMELS entries (most likely, version>=1.8.0).
Please let me know if:

• NXspm/sts/stm/afm etc should be removed from the filter, as they have a dedicated app with more suitable options
• NOMAD CAMELS should be mentioned more/less/not at all (currently only menu/protocols(NOMAD CAMELS and protocol column, which is not shown by default) have filters that work only for them)
• Any functionality / descriptions shall be added or improved
• Any way to replace explicit list of classes inheriting from NXsensor_scan with something more automated exists

For tests, files from corresponding example uploads will work. Test CAMELS files can be found here: https://box.hu-berlin.de/d/2812ff0b8104478ba160/ (just put any of them in an upload without any extra files/schemas)

[RubelMozumder]

You can extend the nexus_app instead of having another app in pynxtools. I think that is what you wanted to do.

[GinzburgLev]

Now this is not a new app, but an update for existing NeXus app (PR name changed accordingly). I tried to include the comments from today discussion. Several remaining issues that I was not able to fix:

1. For every widget/menu item except entry_type, if I select more than one option, the search query is A OR B. For entry_type, it is A AND B. I do not know what this depends on.
2. end time has not been added - currently for start time I use data.ENTRY[*].start_time and not data.ENTRY[*].start_time__field due to definition for NXsensor_scan not yet updated for pynxtools (still wrong format for the field). There is no corresponding field for end_time. Would be easy to do after the updated definition is made available in pynxtools.
3. Sorting along most columns (such as Start Time) is not possible - according to Lauri, sorting can only be done along scalar fields, so anything within data.ENTRY can not be used for sorting.
4. Appearance of the dashboard on screens with different resolution: currently looks OK on a large screen (3840x2160, scale=150%) - one line of widgets, multiple entries are visible in the search results. On a reasonably small screen (1920x1080, scale=125%) just having a periodic table and no other widgets is too much - one has to scroll down to see search results. I am not sure what kind of compromise I should take.