tools.costs does not allow for module-specific cost reduction scenarios and values

[measrainsey]

Currently, for non-energy modules within the costs tool, the only module-specific inputs that are allowed are the ones specified in the tech_map.csv file. For cost reduction values and scenarios, the tool with either (a) use the mapped energy technology's cost reduction values if an energy technology is specified, or (b) assume the cost reduction values are 0.

It would be better to allow for the specification of cost reduction values and scenarios for module-specific technologies, so they are not limited to just whatever the mapped energy technology experiences.

The best way to do that is probably to change the tool so that if cost_reduction.csv and scenarios_reduction.csv values are specified in a non-energy module, then use the values in those CSVs as priority. If those CSVs are not provided or if a non-energy module technology does not exist in the cost_reduction.csv or scenarios_reduction.csv files, then use the mapped energy technology's reduction values and scenarios.