Adding enhanced error handling for invalid column names in coordinate sources

[staudtMarius]

Resolves #670

[sebastian-peter]

Please also check out the SonarQube warnings. To solve them, it could be helpful to check out how org.slf4j.Logger can format log messages with supplied objects

[sonatype-lift]

🛠 Lift Auto-fix

Some of the Lift findings in this PR can be automatically fixed. You can download and apply these changes in your local project directory of your branch to review the suggestions before committing.¹

# Download the patch
curl https://lift.sonatype.com/api/patch/github.com/ie3-institute/PowerSystemDataModel/807.diff -o lift-autofixes.diff

# Apply the patch with git
git apply lift-autofixes.diff

# Review the changes
git diff

Want it all in a single command? Open a terminal in your project's directory and copy and paste the following command:

curl https://lift.sonatype.com/api/patch/github.com/ie3-institute/PowerSystemDataModel/807.diff | git apply

Once you're satisfied, commit and push your changes in your project.

Footnotes

1. You can preview the patch by opening the patch URL in the browser. ↩

[sebastian-peter]

Ok I just realized we already have a validation in Factory#validateParameters, which is called by Factory#get(D), which is called everytime that any entity is parsed from some source. The problem with IdCoordinateSources is that these validations are called after some other things, like duplicate removal, happened, that already access the data and fail if some column is missing.

Looking at Factory.get() as a whole, I'd describe two main issues:

1. validation is sometimes, like in the case of IdCoordinateSource, called too late
2. validation is executed for every single data point parsed from Factory.get(), which is pretty costly

So I think there's a way to fix both at the same time: Validate column names once during initialization (and early enough). Opened up a new issue here: #849

With regards to this PR: We could merge it to fix the problem in IdCoordinateSource, but we then have to remember removing this again once validation is fixed in general.

@staudtMarius @t-ober @danielfeismann

[staudtMarius]

Will be resolved in #926.