feat: implement Jira OAuth integration and connector routes

- Added support for Jira OAuth with new environment variables for client ID, client secret, and redirect URI.
- Implemented Jira connector routes for OAuth flow, including authorization and callback handling.
- Enhanced Jira connector to support both OAuth 2.0 and legacy API token authentication.
- Updated Jira indexing logic to utilize OAuth credentials with auto-refresh capabilities.
- Removed outdated Jira UI components and adjusted frontend logic to reflect the new integration.

surfsense_web/hooks/use-connector-edit-page.ts

@@ -447,6 +447,16 @@ export function useConnectorEditPage(connectorId: number, searchSpaceId: string)
 					}
 					break;
 				case "JIRA_CONNECTOR":
+					// Check if this is an OAuth connector (has access_token or _token_encrypted flag)
+					const isJiraOAuth = !!(originalConfig.access_token || originalConfig._token_encrypted);
+					
+					if (isJiraOAuth) {
+						// OAuth connectors don't allow editing credentials through the form
+						// Only allow name changes, which are handled separately
+						break;
+					}
+					
+					// Legacy API token connector - allow editing credentials
 					if (
 						formData.JIRA_BASE_URL !== originalConfig.JIRA_BASE_URL ||
 						formData.JIRA_EMAIL !== originalConfig.JIRA_EMAIL ||