Better logging in the CSVURLModule

[Dtphelan1]

Summary

This PR addresses STEAM-670: 'CSVURLModule should validate the the URL it receives is a valid URL'. Upon closer inspection, it doesn't look like we do the level of validation we expected in the CSVFileModule. Accordingly, all this task takes up is better logging in fillDataCache logic.

New behavior

When a URL is provided that cannot be used successfully in CSV extraction, error messages are logged to the console. Additionally, debug messages have been added throughout the fillDataCache routine.

Code changes

• Logs added throughout the fillDataCache function.

Testing guidance

• With a URL-enabled csv extractor, run the tool with a valid URL and ensure that extraction works.
• With a URL-enabled csv extractor, run the tool with an invalid URL and ensure that the error message logs as expected.

Below is an example (courtesy of @julianxcarter ) of a valid URL extractor config

{
      "label": "cancerDiseaseStatus",
      "type": "CSVCancerDiseaseStatusExtractor",
      "constructorArgs": {
        "url": "https://raw.githubusercontent.com/mcode/mcode-extraction-framework/main/test/sample-client-data/cancer-disease-status-information.csv"
      }
    }

[dmendelowitz]

This looks good to me! Just had one minor comment

[jafeltra]

The changes here make sense and I get the appropriate log messages. I have one broader question that I'm not sure if was discussed previously or not.

[jafeltra]

Thanks for making those changes!

[jafeltra]

@dmendelowitz do you still approve with the minor changes made since you last approved? Just wanted to give you a chance to take a look before I merged!