Fix: Initialize originalInput in OperationParams

[tallesborges]

Summary

• Added initialization of $originalInput property in the init method of OperationParams class.
• This fix addresses the issue: "Typed property GraphQL\Server\OperationParams::$originalInput must not be accessed before initialization".
• The change ensures that $originalInput is properly set from the BaseOperationParams object during initialization.
• This prevents potential errors when accessing $originalInput and maintains consistency with other properties initialized in the init method.

---

Type of change:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Misc. change (internal, infrastructure, maintenance, etc.)

Checklist:

• Existing tests have been adapted and/or new tests have been added
• Add a CHANGELOG.md entry
• Update the README.md
• Code style has been fixed via composer fix-style

[mfn]

@tallesborges test are failing, can you check?

[tallesborges]

@mfn, to be honest, I'm not sure if it's necessary to keep the baseOperationParams in that class. I've removed the it, and all tests passed.

[mfn]

This change still leaves a discrepancy with \Rebing\GraphQL\Support\OperationParams::getOriginalInput(), which accesses the parent one and not the shallow copy array of our class.

Can you better explain you use case which triggered all of this?

[tallesborges]

It aims to fix the ValidateOperationParamsMiddleware; if an array is used as a variable, it crashes instead of returning the validation error message.

[tallesborges]

any comments @mfn ?

[mfn]

No, sorry, I still don't understand the intention of the change :/