Sampling profiler - adding configuration to select target directory for profiling files

## Is your feature request related to a problem?

Our sampling profiler creates both JFR and activation-events files as part of its execution process.
By default, these files are created in the default tmp file directory, but there may be cases where this may cause issues.
In one known case, a `java.nio.file.FileSystemException` was encountered when using the sampling profiler on a system that uses Azure file share. This may be related to I/O rate limiting when using such systems with the sampling profiler (which can be I/O intensive), or some other unknown issue like improper support for writing to such file shares through direct byte buffers.
## Describe the solution you'd like

Adding a config option to select alternative directory for the Sampling Profiler files.
## Describe alternatives you've considered

Catch errors and try alternative directories, e.g. a subdirectory in the agent installation directory.

Nell’issue non sono indicati file o test. Inizia individuando il codice del sampling profiler che crea i file JFR e activation-events, quindi segui come viene definita e utilizzata la relativa configurazione. Il lavoro è completo quando gli utenti possono selezionare una directory alternativa per entrambi i tipi di file di profiling e il comportamento predefinito esistente rimane invariato.

Scritto dal modello di indicizzazione a partire dal testo della issue.