Add default impl for Storage::range

[chipshort]

first step of #2193

[aumetra]

Should we return an empty range or should we panic with unimplemented!() like we do in, for example, the cryptography APIs?

cosmwasm/packages/std/src/traits.rs

Lines 188 to 194 in 7df4a7b

	fn bls12_381_aggregate_g1(&self, g1s: &[u8]) -> Result<[u8; 48], VerificationError> {
	// Support for BLS12-381 is added in 2.1, i.e. we can't add a compile time requirement for new function.
	// Any implementation of the Api trait which does not implement this function but tries to call it will
	// panic at runtime. We don't assume such cases exist.
	// See also https://doc.rust-lang.org/cargo/reference/semver.html#trait-new-default-item
	unimplemented!()
	}

I'm not sure how I feel about silently failing with a technically incorrect default value, we should probably crash loudly, letting them know something's up

[webmaster128]

Yeah let's create a panicking implementation. We might even want to use a helpful panic message if it is optimized out if iterator is set.

[chipshort]

Good point. I agree it's probably better to panic here.

[webmaster128]

I think we should have a CHANGELOG entry, but change looks good to me