Fix write_error function implementation in handlers

[akchinSTC]

Signed-off-by: Alan Chin akchin@us.ibm.com

Fixes select changes that went into #3038, causing issues with the Mixins in our handlers.
Check and suppress CodeQL warnings if they pop up.

What changes were proposed in this pull request?

How was this pull request tested?

Developer's Certificate of Origin 1.1

   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

[ptitzler]

LGTM! Confirmed that write_error is no longer invoked anywhere. Also verified that the related issues reported in #3077 and #3066 are no longer occurring.

[kevin-bates]

@akchinSTC - to address the the code QL issues, I think your previous version was close.

Rather than have the delegation be HTTPErrorMixin().write_error(params), it only needed to be HTTPErrorMixin.write_error(params). That is, it was the instance creation that was the cause of the issue.

Rather than dismiss all of the alerts (and hope they don't return), I guess I'm more inclined to try the recommended fix of pinning the write_error() to HTTPErrorMixin.