Add python lockfile creation to new releases

[akchinSTC]

Dependent on #3038

Per LFAI onboarding, releases need to be reproducible. In addition to the yarn.lock file, the release process will now include a python lockfile (requirements.txt) generated at build time which includes explicit listing direct and indirect dependencies and their hash signatures.

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.

[kevin-bates]

Is something flagging these as necessary? Seems like write_error() resolution would be satisfied by the mixin.

[akchinSTC]

CodeQL is showing warnings for this. seems they want you to explicitly define which method we use despite it always resolving from left to right in terms of inheritance. Guess its for clarity.