Allow bespoke to read list for resource input

[ppinchuk]

Allow bespoke class to ingest list as resource file, so that you can use

"res_fpath": [
    "/datasets/WIND/conus/v1.0.0/wtk_conus_*.h5",
    "/datasets/WIND/HRRR/hrrr_conus_*.h5",
]

in your bespoke config. Note that vanilla reV instead requires you to list the files out individually. This is because vanilla generation allows brackets {} in the file path that would get filled in by the analysis_years input, so it would be ambiguous which years to use for which file path if the input was:

"resource_file": [
    "/datasets/WIND/conus/v1.0.0/wtk_conus_{}.h5",
    "/datasets/WIND/HRRR/hrrr_conus_{}.h5",
]

(i.e. does 2007 below with WTK or HRRR? What about 2015?, etc).

This PR includes tests for list input, but this use pattern was also tested in production for FY24 SS with WTK+BCHRRR runs.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.68%. Comparing base (f4b0b40) to head (81befce).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #461      +/-   ##
==========================================
+ Coverage   87.64%   87.68%   +0.03%     
==========================================
  Files         122      122              
  Lines       18155    18156       +1     
==========================================
+ Hits        15912    15920       +8     
+ Misses       2243     2236       -7     

Flag	Coverage Δ
unittests	87.68% <100.00%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ppinchuk]

@grantbuster This PR moves to using MultiYearWindResource exclusively in bespoke. I haven't run across any issues in doing so in the tests or production. Any edge case you could think of where we would definitely want to use the basic WindResource file handler?