Additional fuel types for Generator:*Turbine objects

[shorowit]

Pull request overview

Allows additional fuel types for Generator:CombustionTurbine and Generator:MicroTurbine.

Tested locally that the additional fuels correctly show up in End Uses output table as well as the appropriate meter/variable outputs in eplusmtr.csv and eplusout.csv. Here is an example test file I used (minor changes from ExampleFiles/Generators.idf):
Generators-FuelOilNo2.idf.txt

Pull Request Author

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

• Title of PR should be user-synopsis style (clearly understandable in a standalone changelog context)
• Label the PR with at least one of: Defect, Refactoring, NewFeature, Performance, and/or DoNoPublish
• Pull requests that impact EnergyPlus code must also include unit tests to cover enhancement or defect repair
• Author should provide a "walkthrough" of relevant code changes using a GitHub code review comment process
• If any diffs are expected, author must demonstrate they are justified using plots and descriptions
• If changes fix a defect, the fix should be demonstrated in plots and descriptions
• If any defect files are updated to a more recent version, upload new versions here or on DevSupport
• If IDD requires transition, transition source, rules, ExpandObjects, and IDFs must be updated, and add IDDChange label
• If structural output changes, add to output rules file and add OutputChange label
• If adding/removing any LaTeX docs or figures, update that document's CMakeLists file dependencies

Reviewer

This will not be exhaustively relevant to every PR.

• Perform a Code Review on GitHub
• If branch is behind develop, merge develop and build locally to check for side effects of the merge
• If defect, verify by running develop branch and reproducing defect, then running PR and reproducing fix
• If feature, test running new feature, try creative ways to break it
• CI status: all green or justified
• Check that performance is not impacted (CI Linux results include performance check)
• Run Unit Test(s) locally
• Check any new function arguments for performance impacts
• Verify IDF naming conventions and styles, memos and notes and defaults
• If new idf included, locally check the err file and other outputs

[mitchute]

This looks straightforward. I'm not seeing anything that should cause problems with recent merges, but I merged in develop one more time just to get the CI instances off of dead center. I'll run some tests, but I think this could go in shortly. IDD-BDFL (@mjwitte), do you want to take a quick look at the IDD changes here before this goes in?