[Feature] Add new /temp/ Application Path instead of using /generated/temp/ for temporary files

[blakefennimore]

Is your feature request related to a problem? Please describe.
During content generation, the path /generated/tmp/ is used.
I have an Unraid NAS server with SSD drives setup as its "Cache" in addition to its standard disk "Array".
I use the Array for my /generated/ path. This works well as once the content has been generated, there is no reason to use the more efficient (but smaller sized) Cache. But for /generated/tmp/ using the Array is not as performant and causes more wear and tear on my spinning disks, vs. a path that is on the Cache.

Describe the solution you'd like
A new Application Path named something like /temp/ that would be used instead of the path /generated/tmp/ (and any other paths that are used in a similar transient capacity, if there are any others).

Describe alternatives you've considered
I cannot think of an alternative solution. It is not a critical issue, so I have been just accepting it.

Additional context
I am new to stash, so I was surprised that the existing Application Path of /cache/ was not already used for temporary file purposes. But I suppose the term "cache" can have a lot of different meanings.