Max/min parsing function

[alfarj83]

Added function to parse min/max values in the data.

With the new function, the line reading tests should no longer ignore the minimum and maximum values of the data.

Partly addresses #984 by adding needed test code.

Type of change: T-enhancement

(Check the ones that apply by placing an "x" instead of the space in the [ ] so it becomes [x])

• [ ] Note merging this changes the database configuration.
• [x] This change requires a documentation update

Checklist

(Note what you have done by placing an "x" instead of the space in the [ ] so it becomes [x]. It is hoped you do all of them.)

• [x] I have followed the OED pull request ideas
• [x] I have removed text in ( ) from the issue request
• [x] You acknowledge that every person contributing to this work has signed the OED Contributing License Agreement and each author is listed in the Description section.

Will need to test if the function works by replacing the old line tests.

[huss]

Thanks to @alfarj83 for this pull request. A few thoughts:

• src/server/test/web/readingsData/readingsLineMinMaxMeterQuantity.js has the same name as src/server/test/web/readingsLineMinMaxMeterQuantity.js. It seems to have issues and is in the wrong directory. I suspect is is an old version that should be deleted.
• src/server/test/web/expected_line_minmax__ri_15_mu_kWh_gu_kWh_st_2022-08-25000000_et_2022-10-25000000.csv should be in the directory src/server/test/web/readingsData/. I believe that is why the CI test failed on GitHub.
• The test has "L3: " but since it is a new test it should have a new name. Why don't we use "LM3:" for line min/max.

Once these are resolved, I will do a careful read/test of the code. Let me know if you have any questions.

[huss]

I just made a very small change to the mocha description so line with min/max is different. I should have told you to do that so I just did it.