separate options parsing for byteTrace and visitTrace functions

[alexzurbonsen]

Triage

Type of change

Please select any of the below items that are appropriate.

This pull request:

• Adds a new carbon estimation model to CO2.js
• Adds new functionality to an existing model
• Fixes a bug with an existing model implementation
• Add other new functionality to CO2.js
• Add new data to CO2.js
• Improves developer experience for contributors
• Adds contributors to CO2.js
• Does something not specified above

Related issue/s

Please list below any issues this pull request is related to.

• parseOptions validates args it is not supposed to get for perByte(Trace) functions #224

Docs changes required

Do any changes made in this pull request require parts of the CO2.js documentation to be updated?

• Yes
• No
• I don't know

If you answered "Yes", please create an corresponding issue in our Developer Documentation repository.

Describe the changes made in this pull request

Context: see #244

Summary:
This PR splits options parsing into two separate functions, one for the perByteTrace function and one for the perVisitTrace function such that only the options relevant to the function are parsed.

Alternatives: considered: introduce a flag parameter in the existing function to return early when the function is called from perByteTrace. To me this seems less clear, but it would be less invasive.
Also one could create another parsing function for the additional visit options, but not sure that is desirable.

[alexzurbonsen]

I have made the change, but I cannot install the project locally. There is a build failure in one of the dependencies that I do not have the time to figure out. Let's see what the ci says.

[alexzurbonsen]

I didn't understand yet, why the unit tests are failing. The computed values are always a bit off. Not sure if I made a mistake in the option parsing or if some other inputs evolved. but not sure why that should affect versioned older builds.