fix: set resourceRef before resolving query input parameters

[eskenazit]

Related Issue

Closes #206

---

What does this PR do?

In OperationStepExecutor.findClientRequestFor(), resolveInputParametersToRequest() was called before setResourceRef(). For in: query parameters, the resolver appends the query string to the current resourceRef, which was still null at that point, producing null?status=active. The subsequent setResourceRef(clientResUri) then overwrote it, silently dropping the query string.

Fix: moved setResourceRef and setMethod before the two resolveInputParametersToRequest calls.

Also fixed HeaderQueryIntegrationTest: the existing assertion was a tautology (a || !b where b was always false), so the test always passed. Replaced with two explicit assertions and added a comment explaining the intent of the q=%22 guard.

---

Checklist

• CI is green (build, tests, schema validation, security scans)
• Rebased on latest main
• Small and focused — one concern per PR
• Commit messages follow Conventional Commits

---

Agent Context (optional)

agent_name: GitHub Copilot
lml: Claude Sonnet 4.6
tool: VS Code Copilot Chat
confidence: high

[jlouvel]

LGTM