Warn for Mismatched Leap Year Support

[Myoldmopar]

Issue overview

Thread is here: https://github.com/NREL/EnergyPlus/pull/7199/files/8d9cc1b3690e4396ccf3e4eb2caa5db4f1a8a615#diff-3db4af63e54cde7a34f2fab72ff096fdR10015 but basically, add a warning if run period requests a leap year but the weather file does not support it. Right now it silently runs.

Details

Some additional details for this issue (if relevant):

• Platform (Operating system, version)
• Version of EnergyPlus (if using an intermediate build, include SHA)
• Unmethours link or helpdesk ticket number

Checklist

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

• Defect file added (list location of defect file here)
• Ticket added to Pivotal for defect (development team task)
• Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)

[jasondegraw]

Some of this is mentioned over in the other thread, but for clarity:

• This should wait until the WeatherManager is refactored.
• The old behavior (before the year awareness work in Merge RunPeriod and RunPeriod:CustomRange #6478) was more silent than not, and that was preserved in the RunPeriod merge
• Hopefully, the refactored weather will be more like the other schedules (i.e. there's always a leap day available). Suggestions have been made as to how to get a Feb29 from an EPW that doesn't have one, but there was no consensus and that'll need to be solved. Just doing that would help with a lot of things, and it would change what we need to warn about.