JPERF-790: Fix Jira Standalone testing for pre version 8.9.0

For Jira pre 8.9.0 if the instance has no access to its own HTTP the dashboard view may freeze (in our case it was after log in, however it may be related to dataset config).
This access to self is described as required in the setup documentation https://confluence.atlassian.com/jirakb/configure-linux-firewall-for-jira-applications-741933610.html and it was missed in implementation of aws-infrastructure 2.24.0

> 4 - Allowing connections to JIRA from itself (to ensure you don't run into problems with [gadget titles showing as __MSG_gadget](https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html))
> ```iptables -t nat -I OUTPUT -p tcp -o lo --dport 80 -j REDIRECT --to-ports 8080```

CHANGELOG.md

@@ -22,6 +22,11 @@ Dropping a requirement of a major version of a dependency is a new contract.
 
 ## [Unreleased]
 
+### Fixed
+- Grant Jira access to its own HTTP port in `StandaloneFormula`. Fix [JPERF-790].
+
+[JPERF-790]: https://ecosystem.atlassian.net/browse/JPERF-790
+
 ## [2.25.0] - 2022-01-14
 [2.25.0]: https://github.com/atlassian/aws-infrastructure/compare/release-2.24.0...release-2.25.0
 

src/main/kotlin/com/atlassian/performance/tools/awsinfrastructure/api/jira/StandaloneFormula.kt

@@ -224,6 +224,10 @@ class StandaloneFormula private constructor(
             )
         )
 
+        val selfDashboardAccess = executor.submitWithLogContext("self dashboard access") {
+            ForIpAccessRequester { jiraPublicIp }.requestAccess(jiraNodeHttpAccessProvider)
+        }
+
         val externalAccess = executor.submitWithLogContext("external access") {
             accessRequester.requestAccess(jiraAccessProvider)
         }
@@ -249,6 +253,10 @@ class StandaloneFormula private constructor(
         val databaseDataLocation = setupDatabase.get()
         val node = time("start") { provisionedNode.start(emptyList()) }
 
+        if (!selfDashboardAccess.get()) {
+            logger.warn("It's possible that Jira doesn't have HTTP access to itself. Dashboards may not work.")
+        }
+
         if (!externalAccess.get()) {
             logger.warn("It's possible that defined external access to Jira resources (e.g. http, debug, splunk) wasn't granted.")
         }