Documentation/00 update

[RHammond2]

This addresses the comments from #194 and therefore closes #195.

Changes:

• The QA module was updated to address the UTC conversion incorrectly shifting at both the European and US daylight savings time (DST) shifts
• Adds a fontsize to the DST plotting routine so that it's not oversized compared to the plots themselves
• Addresses the comments from #195
  • There was in fact a logic error with the repeated values/unresponsive data analysis, so I've updated the logic here and redone the plots to be more clear (though I'm open to feedback on the nomenclature for the axes and commentary)
  • Good catch on the newly found gaps, this was in fact a bug, likely due to a dependency version change somewhere
  • I've hopefully updated the commentary sufficiently, but I'll let you be the judge of that one.

@ejsimley this review could either be a more detailed review, or a shorter review that ultimately gets brought back up in a comprehensive review of our examples and documentation. In either case, this PR isn't holding up other processes, so you're welcome to take your time with it now.

[RHammond2]

@ejsimley This should fix up the remaining errors in the code and language in the notebook. I just removed the offending comment line for "create additional turbine objects" because that is a remnant from whoever originally wrote the notebook and it didn't seem to mean anything to me. You'll notice an error in the last section, which I believe is addressed in #198, and if not I'd like to address it separately anyway in a small PR.

[ejsimley]

@RHammond2, the documentation looks great now. I think this is fine to merge whenever you're ready. A couple points to consider, though are:

• When you get a chance, change qa.dalyight_savings_plot to qa.daylight_savings_plot
• For my comment "Step 6: print(PlantMetaData.__doc__): I suggest we include at least plant capacity and number of turbines as plant metadata fields, since they were used in v2 and would probably continue to be useful." Even if this isn't addressed in this PR, let's keep this in mind as something we might need to address if other analysis methods use these other plant attributes.
• Regarding the comment "Step 6: The last comment is for the following cell. I'm curious why there are error messages for the "time" columns for meter, curtail, and reanalysis data types here, but there were no errors when only "MonteCarloAEP" was being validated (even though MonteCarloAEP uses these data types too)". I see it's no longer throwing an error because of the time columns, but I'm still confused why there are other errors for missing fields in meter, curtail, and reanalysis, since these data types would be used for MonteCarloAEP as well (but there were no errors identified when validating MonteCarloAEP). Also, I think it would be helpful to print which analysis method the errors are being identified for. Otherwise it isn't clear what needs to be fixed to be able to run each each analysis method.

[RHammond2]

@ejsimley, thanks for catching the typo and all of the other thoughtful comments along the way! As for capacity, that's included in #200, but I forgot to mention that in my previous comment.

I'm thinking that I fixed the underlying issue causing the what you're seeing the last comment in #198, so I'd like to test that out after this PR is merged, and address it in its own PR where the changes aren't coming from many directions.