Implement support for Azure DevOps Server and GitHub Server (onpremise)

[Copilot]

This PR implements support for onpremise installations of Azure DevOps Server and GitHub Server by adding configurable custom hostname support to the VOCE extension.

🎯 Problem

The extension was hardcoded to work only with cloud services (github.com and dev.azure.com), preventing usage with enterprise onpremise installations.

✅ Solution

Added two new VS Code configuration options that enable onpremise support:

{
  "voce.azd_customhostname": "devops.company.com",
  "voce.gh_customhostname": "github.company.com"
}

🔧 Implementation Details

GitHub Server Support

• Dynamic hostname detection from configuration in src/github/gitHub.ts
• Updated Octokit initialization to use custom baseUrl for API calls (https://{hostname}/api/v3)
• Flexible URL parsing with regex patterns that use configured hostname instead of hardcoded github.com

Azure DevOps Server Support

• Dynamic hostname detection from configuration in src/azd/azd.ts
• New utility functions in src/azd/azDevOpsUtils.ts:
  • getAzureDevOpsOrgUrl() - Organization URLs
  • getAzureDevOpsWorkItemUrl() - Work item URLs
  • getAzureDevOpsPullRequestUrl() - Pull request URLs
• Replaced all hardcoded URLs in work item and pull request functions

🌐 URL Transformation Examples

Before (Cloud only):

Azure DevOps: https://dev.azure.com/myorg/myproject/_workitems/edit/123
GitHub:       https://github.com/owner/repo (API: api.github.com)

After (Custom hostnames):

Azure DevOps: https://devops.company.com/myorg/myproject/_workitems/edit/123
GitHub:       https://github.company.com/owner/repo (API: github.company.com/api/v3)

🚀 Usage

The extension automatically detects onpremise mode when custom hostnames are configured:

@voce /azd-workitem !123     → Uses devops.company.com
@voce /gh-issue !456         → Uses github.company.com
@voce azdo:org/proj !789     → Uses configured Azure DevOps hostname
@voce gh:owner/repo !101     → Uses configured GitHub hostname

✅ Backward Compatibility

• Default behavior unchanged - uses cloud services when no custom hostnames configured
• No breaking changes - all existing commands and prompts work without modification
• Automatic fallback - empty/unset hostnames default to github.com and dev.azure.com

🧪 Testing

• ✅ Compilation and linting pass successfully
• ✅ Regex pattern validation for both HTTPS and SSH URLs
• ✅ URL construction utility functions validated
• ✅ Documentation and demo scripts created

Fixes #70.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[norschel]

To address the issue, we need to ensure that the literal dot (.) in ssh.dev.azure.com is properly escaped when constructing the regex. This can be achieved by applying the same escaping logic as done for azDevOpsHostname earlier in the code. Specifically, the replace(/\./g, '\\.') method should be applied to sshHostname before it is used as part of a regex.

Changes will be made to the line constructing escapedSshHostname on line 42 to ensure the dot is escaped. This ensures the regex matches the exact hostname without allowing unintended matches.

---

To fix the issue, we need to ensure that backslashes in the customHostname (or the default value "dev.azure.com") are escaped before constructing the regular expression. This can be achieved by chaining a .replace(/\\/g, '\\\\') call before escaping dots. This approach is consistent with the escaping logic used elsewhere in the file (e.g., line 13).

The updated code will:

1. Escape backslashes first using .replace(/\\/g, '\\\\').
2. Escape dots using .replace(/\./g, '\\.').

The fix will be applied to line 33 where azDevOpsHostname is defined.

---

To fix the issue, we need to ensure that the escaping is performed correctly and consistently. Specifically:

1. The backslash (\) should be escaped only once, and this escaping should occur after all other characters (like .) have been escaped.
2. The order of escaping operations should be adjusted to avoid double-escaping. For example, the . character should be escaped first, followed by the \ character.

The fix involves reordering the escaping operations and ensuring that backslashes are escaped only once, after all other characters have been processed.

---