Remove python file generation from Ntuple Wizard -- it will be handled in the Ntupling Service backend

Change Decay search to be case insensitive

See merge request !71

Update alpha with recent changes

See merge request !70

Update package-lock and ignore sourcemap locally

See merge request !69

Improve UX for adding DecayTreeTuples

See merge request !67

fix wg issue

See merge request !68

Adds a visual indicator that the user must add DecayTreeTuples before
they can download or submit their request.

Add package-lock.json

See merge request !66

Update metadata URL

See merge request !65

Add CSRF token prop

See merge request !64

Make hiding the upload buttons configurable

See merge request !62

Fix setting the info.yaml inform field when email is known

See merge request !61

Upload config from files stored on ntupling service

Closes #47

See merge request !55

Related to #47

Fixed issue in uploading info.yaml config when multiple DTT config files run over the same data set in the bookkeeping

Fixed issue with uploading config from info.yaml. It should be general enough to capture arbitrary configurations now.

Merge branch 'dillon/uploadZIP' of https://gitlab.cern.ch/lhcb-dpa/wp6-analysis-preservation-and-open-data/lhcb-ntuple-wizard-frontend into dillon/uploadZIP

Removing requirements to disable button for uploading production config. It can now be uploaded at any point while on the main page.

Stripping-line content as functions

See merge request !53

Removed code to exclude internal lines, I will factorize that into another branch for demonstrative purposes. This MR is ready to go unless we want to change the way files are read in from a list (from a single production) to a zip file (of either a single production or all available productions)

Updated demo function for excluding internal LHCb stripping lines to delete particular lines from decays rather than removing decays alltogether than coincide with a forbidden line. The demonstration uses a simple toggle switch to exclude decays, but there is a caveat that the lines are not restored when the switch is toggled back off. This can be easily fixed, but it is not necessary, as any real implementation will only require hiding forbidden lines (no toggle switch). In the future, the list of forbidden stripping lines can be delivered via a Metadata context from the backend output.

Add demo functionality for restricting stripping lines baseed on an input list. Also for the discussion on 10/09/2023

Had to add parentCallbackRows to handleAddRow in order for the uploaded application state to be passed properly to the DescriptorSearch page.

Update dev branch

See merge request !58

Several request creation modifications

See merge request !57