"Could not find atlassian-jira.log" is seen on the System info page when the log file is redirected outside of JIRA_HOME

Issue Summary

If an admin redirects atlassian-jira.log file outside of JIRA_HOME, then Jira is unable to find log location and showing "Could not find atlassian-jira.log" on the System info page. This is having an impact on the ATST plugin while generating support.zip and skipping all application logs.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Install 9.12.2 and update the log4j2.xml to redirect log file as mentioned here
2. Install 9.4.14 and update log4j.properties to redirect log file as mentioned here
3. Navigate to System info (secure/admin/ViewSystemInfo.jspa) and notice that the log file location couldn't be determined.
4. Generate support.zips on both env and notice that the application-logs directory itself is missing in the support.zip on 9.12.2 and not just atlassian-jira.log
5. On 9.4.14, you will be able to see atlassian-jira.log as well as other log files.

Expected Results

• Jira should be able to locate the log file location using the file appender configuration
• ATST should be able to include the application logs

Actual Results

The below exception is seen if we enable the DEBUG for com.atlassian.jira.util.system

2024-03-12 13:41:38,902+0000 http-nio-8080-exec-16 url: /jira/plugins/servlet/troubleshooting/view/hercules/view; user: admin DEBUG admin 821x1182x4 ep0pak 172.29.217.33,172.50.0.2 /plugins/servlet/troubleshooting/view/hercules/view [c.a.j.util.system.ExtendedSystemInfoUtilsImpl] Could not find atlassian-jira.log.
2024-03-12 13:41:39,007+0000 http-nio-8080-exec-14 url: /jira/plugins/servlet/troubleshooting/view/atst-detect-issues/view; user: admin DEBUG admin 821x1181x3 ep0pak 172.29.217.33,172.50.0.2 /plugins/servlet/troubleshooting/view/atst-detect-issues/view [c.a.j.util.system.ExtendedSystemInfoUtilsImpl] Could not find atlassian-jira.log.

Workaround

Showing the correct location on the System info page is not possible, but creating a symlink for atlassian-jira.log in the default log location(JIRA_HOME/log) can help to mitigate the support.zip creation issue.