A job which runs for more than 4 frames (e.g. runtime navmesh baking) produces warnings about JobTemp memory being allocated for too long, even if all parts of the job itself are using Persistent memory.

Steps to reproduce:
1. Open the attached user's project "workbench-trunk.zip"
2. Open "ai-repro.unity" Scene
3. Enter Play Mode
4. Observe the warning messages in the console about the memory being leaked:
Internal: JobTempAlloc has allocations that are more than the maximum lifespan of 4 frames old - this is not allowed and likely a leak

Expected results: Runtime navmesh update does not leak JobTemp memory
Actual results: Runtime navmesh update leaks JobTemp memory

Reproducible in: 2023.1.0a1, 2023.1.7f1, 2023.2.0b4, 2023.3.0a1
Not reproducible on: 2021.3.29f1, 2022.3.7f1

Environment tested on: Windows 10

Notes:
-To trigger the bug, your framerate needs to be high enough relative to the time taken by the navmesh bake. If it doesn't happen for you, try modifying NavMeshUpdater.cs line 23 to increase the number of extra shapes added to the bake.