Feature request: Enhanced Jenkins job configuration for airgapped and non-airgapped environments

[coderabbitai]

Background

Currently, the Jenkins job agent configuration () uses a simple input field for manually entering Jenkins job URLs, which works well for airgapped environments where direct server connection isn't available.

Feature request

Enhance the Jenkins job configuration to handle two distinct scenarios:

1. Airgapped environments (current implementation)

• Continue supporting manual URL input for environments without direct Jenkins server access
• Minimal validation to accommodate various Jenkins URL patterns

2. Non-airgapped environments

• Implement a dropdown selection interface when the Jenkins server is accessible
• Allow users to browse and select from available Jenkins jobs
• Possibly fetch and display additional job metadata

Implementation approach

Create a component structure similar to that can:

• Detect whether the Jenkins server is accessible
• Conditionally render the appropriate interface (manual input or dropdown)
• Provide a seamless experience in both scenarios

Benefits

• Improved user experience for environments with Jenkins server access
• Reduced possibility of input errors
• Consistency with other job agent configuration interfaces

This issue was created based on a code review discussion in PR #408.

/cc @zacharyblasczyk