Should at least attempt to create $JFROG_CLI_TEMP_DIR when it's set and doesn't exist

Is your feature request related to a problem? Please describe.

We're using GitLab CI with fully containerized jobs. So we need to have JFROG_CLI_TEMP_DIR persisted across stages in order for things like Build Info to work. But in order to cache that directory from container to container, we have to set it relative to the directory the build script is running in. But if we don't also add a mkdir ${JFROG_CLI_TEMP_DIR} to the job script, the CLI puts out this error

[Error] open /builds/geo/map/.jftmp/jfrog.cli.temp.-1770276634-261243735: no such file or directory

We don't see these errors when the default temp dir path is used, so it seems that the CLI will create the temp dir if and only if it is the default path.

Describe the solution you'd like to see

If a custom path has been specified and does not exist, the CLI should try to create it.

Describe alternatives you've considered

We're currently manually creating the directory in our job script, but some people don't use the shared CI templates and miss this part then file support tickets.

Start by locating the code that reads JFROG_CLI_TEMP_DIR and creates the default temporary directory. Reproduce the failure with a nonexistent custom path, then verify the CLI attempts to create it while preserving behavior for existing and default paths. Add or update tests for the custom-directory case if the surrounding code has coverage.