refactor: use IPIP-402 param names when GRAPH_BACKEND=true

[lidel]

Ref. ipfs/specs#402

This PR follows a transition plan from #80 to send all versions until every system (lassie, l1) upgrades.

[lidel]

I'd like to ship this to staging, and if no issues, tag a release and ship to prod as well, to unblock other systems and allow them to safely switch to new names.

@aarshkshah1992 Depending on how HTTP cache key is built on L1 and nginx, this may temporarily produce high % of cache misses, impact latency etc. Due to this want to get 👍 from you before shipping this, in case you have any experiment running on staging.

[willscott]

@aarshkshah1992 is okay with this happening - ping him on slack before you deploy to staging

[aarshkshah1992]

@lidel "Depending on how HTTP cache key is built on L1 and nginx, this may temporarily produce high % of cache misses, impact latency etc."

Could you elaborate more on this. Do we have a mitigation plan in place if this does indeed happen i.e. how do we then improve the latency, cache hit percentage etc ? Will we have to roll back the change or do some work on Saturn ?

[lidel]

If Saturn treats URL query and path as opaque string, and used that as cache key, we need to wait for Saturn cache to fill up with the new URLs, and things will get back to normal.

Just warning the metrics may be skewed for a few hours or a day.

[hacdias]

Just to see if I understand what's happening here: we're adding support for IPIP-0402 parameters on the parameters we pass to the backend, right? The gateway itself does not support them but will after we have ipfs/boxo#303. If that is the case, I would rename the PR.