Bug Report: Inconsistent type for provider configuration in config.py

[tiaz0128]

Description

In config.py, some provider configurations are using string type while others are using tuple type. This inconsistency could lead to potential bugs and should be standardized across all providers.

Current Behavior

Some provider configurations are defined as strings while others are defined as tuples:

UPPER_WORDS = {
    # ...
    "pve": ("pve"), # Incorrectly defined as string due to single parenthesis
    "ibm": ("ibm"), # Incorrectly defined as string due to single parenthesis
    # ...
}

Expected Behavior

All provider configurations should consistently use tuple type with proper comma:

UPPER_WORDS = {
    # ...
    "pve": ("pve",), # Properly defined as tuple
    "ibm": ("ibm",), # Properly defined as tuple
    # ...
}

Why This is Important

• Python treats ("pve") as string, not tuple
• ("pve",) is the correct syntax for single-element tuple
• Inconsistent types could cause bugs in code that expects tuples

Additional Context

• Found while reviewing PR related to provider changes
• This issue affects the configuration structure used throughout the application