how to handle the case where combined oracle price is outside of min/max supported price

[moodysalem]

the average ticks added up can exceed min/max tick, which means we can't compute the price because it's less than or greater than 2**128/1

currently we just revert, but it's not clear how we should actually handle this edge case. it is unlikely to be beneficial to succeed in the case that the queried token pairing has a negligible price