Hey folks, thanks for reporting this issue! Your hunch was right, this was related to a fix for Don't reorder request parameters in Edge Functions. I’ve rolled back the fix because it was causing some minor issues, and your argument also makes sense to me. The main point in RFC3986 that we need to adhere to is this:
Percent-encoding a reserved character, or decoding a percent-encoded octet that corresponds to a reserved character, will change how the URI is interpreted by most applications. Thus, characters in the reserved set are protected from normalization and are therefore safe to be used by scheme-specific and producer-specific algorithms for delimiting data subcomponents within a URI.
~ § 2.2 Reserved Characters
You should be seeing the same behaviour across production and netlify dev again on this now.