Added case insensitive capability for field names inside RML definitions

RESTFramework
1

Now field name identification inside RML definitions is case insensitive.

Therefore, now the upper-lower pattern of a field will be ignored!

I.e. yrange, yRange, Yrange, yRANGe, or yranGE will all be identified.

Changes can be found in the following commit 03f47ff.

2

The pipeline fails with this commit.

3

I will look at that. You reverted the commit directly in panda Gitlab repository. Should not be a mirror of LFNA that reproduces whatever it is there?

4

Any commits on SJTU gitlab will be overwritten later-on when syncing with lfna. So it doesn’t matter that I do a revert in SJTU gitab, just to check whether the problem is related to that commit or not.

5

Ok, I cannot do the same, i.e. push to SJTU test commits that will be overridden.

I have pushed to LFNA the following commit

to revert some changes in TRestG4Event.

I understand the actual implementation of TRestG4Event::Initialize may cause problems and needs to be polished, just reverting to check the pipeline green checkmark is right now.