Fix security issues and warnings

[stefanCCS]

Description

For KITODO.PRODUCTION the security issues which are reported on the security tab should be removed (in the meaning of "to be solved").
This is a similar task as we have done already for KITODO.PRESENTATION (see kitodo/kitodo-presentation#893.

At this moment this issue here is just prepared with the aim to have it available for next development fund round.
It might be needed to update this content here, when the next round of development fund is started.

[stefanCCS]

@solth : Please consider to create label "development fund 2025", change the label on this issue to that (2025), and assign this new label for the issue type "task for development fund".

[henning-gerhardt]

For KITODO.PRODUCTION the security issues which are reported on the security tab should be removed.

Your mentioned link is only available for certain persons which have the right to see them. But independent of this link: you can see all the issues if you fork the repository and enable the security scanning from GitHub. The security issues are not solved by removing them from the list they are only "hidden" and still existing and should be solved instead of ignored. Hiding them until and presenting them only on the next round of the development found is in my opinion a bad move.

[stweil]

Related: #5997. Some issues are reported by both static analyzers.

GitHub Code Scanning currently reports 1390 issues, Coverity Scan reports 353 issues.

Codacy reports 95 issues.

[stefanCCS]

For KITODO.PRODUCTION the security issues which are reported on the security tab should be removed.

Your mentioned link is only available for certain persons which have the right to see them. But independent of this link: you can see all the issues if you fork the repository and enable the security scanning from GitHub. The security issues are not solved by removing them from the list they are only "hidden" and still existing and should be solved instead of ignored. Hiding them until and presenting them only on the next round of the development found is in my opinion a bad move.

The purpose of this issue here, is not not intended to "hide" the issue, but to solve these (I have updated the description accordingly.