Bybit EU - API keys created via "Connect to third-party applications" are rejected even after v5 fixes (#7415)

Describe the bug On Bybit EU, API keys created through the "Connect to third-party applications" flow (e.g. Gainium.io EU) are rejected by Hummingbot when trying to connect to bybit_perpetual, even though previous fixes for v5 API were merged (#7415, #7179).

To Reproduce

1. On Bybit EU, create a new API key using "Connect to third-party applications" (selected Gainium.io EU)
2. Enable Read-Write + Trading permissions (Spot + Futures)
3. In Hummingbot v2.15.0 run: connect bybit_perpetual
4. Error appears: Failed to connect API keys / API keys have not been added (or 401 Unauthorized)

Expected behavior Hummingbot should successfully connect to bybit_perpetual and show the account balance.

Actual behavior Hummingbot fails to connect even with correct permissions. The same key works partially on Spot but is rejected on Perpetual.

Environment

• Hummingbot version: 2.15.0 (Docker)
• OS: macOS (Apple Silicon)
• Exchange: Bybit EU (bybit.eu)
• How the key was created: Via "Connect to third-party applications" flow (not direct system-generated key)

Additional context

• Issue #7415 was closed as "completed" in Feb 2025 with the note that the fix would be in v2.4.0.
• The problem seems to be related to how Bybit EU handles keys created through the third-party applications flow (common for EEA users due to MiCA).
• Direct system-generated keys might work better, but Bybit EU often forces users into the third-party flow.

Is this a known limitation of Bybit EU, or is there a recommended way to create API keys for Hummingbot on Bybit EU?

Any workaround would be appreciated.