Re #9682. Changed behavior of interpolation with one value

In the previous commit, I fixed the problem caused by having only one value in the interpolation table by return 0. On second thought, it makes more sense to assume a "constant interpolation" and return the one stored y-value for any x.
Merge branch 'feature/9682_lookup_table_read_multiple_times' into develop