elasticity-f file does not pick DIGSY scenario values

[r-aneeque]

• check and if needed fix so that correct scenario labels are picked for elasticity-f values for CircEUlar scenarios

For DIGSY scenarios, the elasticity-f file does not seem to pick the correct DIGSY labels (at least on my experimental branch transport-runs-2026-w17. I implemented them via changing SSP2 values and that works.

Not important for now, but will be important for CircEUlar runs in the BMT integrated version.
Double-check:

• if the labels for DIGSY were incorrect
• if the issue is fixed on the current development branch with updated CircRUlar labels.

[r-aneeque]

Recurring changes to scenario labels caused this. This file uses the original DIGSY-BEST, DIGSY-BESTEST, DIGSY-WORST, DIGSY-WORSTEST
We went from original DIGSY-BEST (BESTEST) to DIGSY-BEST-C (S) to now DIGSY-BEST-C (S/M).
I will double-check that the scenario labels are consistent for different files (e.g. pdt-cap, load-factor etc.)

[khaeru]

This was caused by some changes on #497, and fixed by later commits on the same branch. I'll link it to that PR so the issue will be closed when the PR is merged.