High heap memory consumption during PDF generations with Itext5.

Build information:
Builds that are known to be affected: Tokyo P2
Builds that are known NOT to be affected: San Diego P9



Issue Description:
After the upgrade from San Diego Patch 9 to Tokyo Patch 2, generating a large PDF report using the iText5 library causes high heap memory consumption.

After upgrading to Tokyo P2 from San Diego P9, when generating a large PDF using the iText5 library, long running API_INT semaphore transactions and high memory consumption can be observed.

iText5 based APIs are deprecated from Sep 2022.We recommended and informed every consumer to switch to iText7 based APIs(https://docs.servicenow.com/bundle/utah-api-reference/page/app-store/dev_portal/API_reference/DocumentBoth/concept/DocumentBothAPI.html#DocumentBothAPI)

Please advise customer to use iText7. All our OOB code have already switched to iText7 which is the direction going forward.

Dev plans to fix the regression issue in PRB1564039. We will also backport to Tokyo Patch 8.

Customer can either switch to iText7 or wait for Tokyo Patch 8.