Local Network Access Checks in Chrome Prevent Setting up GitLab for Jira Cloud app on Self-Managed instance within local IP range
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=581765)
</details>
<!--IssueSummary end-->
<!---
Please read this!
Before opening a new issue, make sure to search for keywords in the issues
filtered by the "regression" or "type::bug" label:
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression
- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug
and verify the issue you're about to submit isn't a duplicate.
--->
### Summary
Customers cannot set up the GitLab for Jira Cloud app with self-managed GitLab instances that are in a local IP range when using Chrome/Chromium-based browsers due to Chrome's Local Network Access (LNA) prompts introduced in Chrome 142.
Allowing "Local Network Access" within site settings for the self-managed instance, atlassian, and GitLab.com does not change behavior. Even with all three set to "allow" the set up fails.
Setting up the integration in Firefox is the current workaround.
Link to chrome blog post on the new feature: https://developer.chrome.com/blog/local-network-access
### What is the current _bug_ behavior?
When setting up the GitLab for Jira Cloud integration, the integration creates a "Failed to load Jira Connect Application ID. Please try again" error when trying to sign into a self-managed GitLab instance. As a result the integration cannot be set up in google chrome.
<!--Describe what actually happens.-->
### What is the expected _correct_ behavior?
Integration is able to be set up without error.
<!--Describe what you should see instead.-->
### Relevant logs and/or screenshots
<!--Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
as it's tough to read otherwise.-->
```
# Sampled from HAR file:
{
"_initiator": {
"type": "preflight",
"url": "https://<gitlab_url>/-/jira_connect/oauth_application_id",
},
"_priority": "High",
"_resourceType": "preflight",
"cache": {},
"request": {
"method": "OPTIONS",
"url": "https://<gitlab_url>/-/jira_connect/oauth_application_id",
"httpVersion": "",
"headers": [
{
"name": "Accept",
"value": "*/*"
},
{
"name": "Access-Control-Request-Headers",
"value": "x-csrf-token,x-requested-with"
},
{
"name": "Access-Control-Request-Method",
"value": "GET"
},
{
"name": "Origin",
"value": "https://gitlab.com"
},
{
"name": "Sec-Fetch-Mode",
"value": "cors"
}
],
...
},
"response": {
"status": 0,
...
"_error": "net::ERR_BLOCKED_BY_PRIVATE_NETWORK_ACCESS_CHECKS",
```
### Patch release information for backports
If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the [patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md).
Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for information about the next patch release, including the targeted versions, expected release date, and current status.
#### High-severity bug remediation
To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances, refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads).
<!--If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"`-->
issue