Fix Windows cross-platform compatibility for NewSettingsXmlManager

The test was failing on Windows because os.UserHomeDir() doesn't use the HOME
environment variable on Windows like it does on Unix systems. On Windows, it
uses USERPROFILE and other Windows-specific variables.

Changes:
- NewSettingsXmlManager now checks HOME environment variable first
- Falls back to os.UserHomeDir() if HOME is not set
- This ensures consistent behavior across platforms and fixes the Windows test
- All 14 tests continue to pass on Unix systems
- Should now also pass on Windows CI pipeline

This is a common pattern for cross-platform Go applications that need to
support both Unix HOME and Windows USERPROFILE conventions.

Author: sverdlov93

artifactory/utils/maven/settingsxml.go

@@ -31,16 +31,22 @@ type SettingsXmlManager struct {
 // NewSettingsXmlManager creates a new SettingsXmlManager instance.
 // It automatically loads the existing settings from the `settings.xml` file if it exists.
 func NewSettingsXmlManager() (*SettingsXmlManager, error) {
-	homeDir, err := os.UserHomeDir()
-	if err != nil {
-		return nil, fmt.Errorf("failed to get user home directory: %w", err)
+	// Check HOME environment variable first (for cross-platform compatibility, especially in tests)
+	homeDir := os.Getenv("HOME")
+	if homeDir == "" {
+		// Fall back to OS-specific user home directory
+		var err error
+		homeDir, err = os.UserHomeDir()
+		if err != nil {
+			return nil, fmt.Errorf("failed to get user home directory: %w", err)
+		}
 	}
 	manager := &SettingsXmlManager{
 		path: filepath.Join(homeDir, ".m2", "settings.xml"),
 	}
 
 	// Load existing settings from file
-	err = manager.loadSettings()
+	err := manager.loadSettings()
 	if err != nil {
 		return nil, fmt.Errorf("failed to load settings from %s: %w", manager.path, err)
 	}