Restarting a Jira instance in Kubernetes disables the Java Flight Recorder as the active_configuration.jfc is destroyed

Issue Summary

In a Kubernetes environment, the file /var/atlassian/application-data/jira/log/jfr/active_configuration.jfc is destroyed on restart. This disables the Java Flight Recorder but does not provide any notification to the admin. In 8.20.x, a health check warning would be triggered to notify the admin that it wasn't running. 

This may also impact any other type of deployment, such as on AWS, if the jira-local-home is treated as ephemeral.

Steps to Reproduce

1. Install Jira in Kubernetes using Atlassian Helm 
2. Confirm the Java Flight Recorder is running. 
3. Restart Jira

Expected Results

Java Flight Recorder will continue to run or if it is unable to start, pop up a notification that it's not running.

Actual Results

 The Java Flight Recorder is disabled with no warning to the admin. 

Workaround

• Persist the log directory where /var/atlassian/application-data/jira/log/jfr/active_configuration.jfc is located.
• A Jira Administrator can turn off and back on JFR through the UI if a node has restarted