[Bug]: StopOrders sizeOverrideSetting and sizeOverrideValue values are different than submitted

[bglownia]

Problem encountered

Stop order submitted with sizeOverrideSetting SIZE_OVERRIDE_SETTING_POSITION are returned as SIZE_OVERRIDE_SETTING_UNSPECIFIED.
sizeOverrideValue is retuned as null

Transactions sent

Data returned from stopOrders graphql API

Observed behaviour

wallet accepts sizeOverrideSetting sent as string or number. Transactions send both with "sizeOverrideSetting":2 and "sizeOverrideSetting":"SIZE_OVERRIDE_SETTING_POSITION" are retuned from stopOrders API with "SIZE_OVERRIDE_SETTING_UNSPECIFIED" value.
"sizeOverrideValue" is sent as {"percentage":"1"} and returned from API as null

Expected behaviour

Stop order should be created and returned with proper sizeOverrideSetting and sizeOverrideValue

Steps to reproduce

Submit stop order with sizeOverrideSetting SIZE_OVERRIDE_SETTING_POSITION
Query stopOrders graphql API.

Software version

v0.76.0-preview.1

Failing test

No response

Jenkins run

No response

Configuration used

No response

Relevant log output

No response

[bglownia]

I just tested it on stagnet. This fix should be included in v0.76.0-preview.2 but it still returns sizeOverrideSetting: SIZE_OVERRIDE_SETTING_UNSPECIFIED and sizeOverrideValue:null

You can try submit position scoped stop order from
https://trading.4353-position-tp-sl.vega.rocks/