Operation credentials should not be global


- {{classname}}::{{nickname}}WithDataImpl is generated for each
operation, and the {{#authMethods}}{{/authMethods}} block inside
the method handles authentication parameters specific to that
operation.
However, using setHeader() made these credentials available to all
other operations.

- The change removes the {{#authMethods}}{{/authMethods}} block
and start using {{>set-auth-query}} and {{>set-auth-headers}} instead.
Credentials are now added to the individual request's headers rather
than the global factory headers.

[ChangeLog][Important Behavior Changes] Fixed a bug when operation
credentials associated with a specific operation were applied globally
and shared with other operations. Credentials are now applied
individually for each operation.

Pick-to: 6.12
Change-Id: I76873a4e5bf5640316b7f1170696320c142e8e9f
Reviewed-by: Ivan Solovev <ivan.solovev@qt.io>
commit3dd23bb9b64d53caa66d4d87bd888e4bac99c65d
parentbc1ec6a89c77d786dff3ceab59a301ee505b5eaf
authorTatiana Borisova <tatiana.borisova@qt.io>
committerIvan Solovev <ivan.solovev@qt.io>
commit timeThu, 22 Oct 2026 08:52:49 +0000