Add Hyperion Instance Management Feature for Easy Switching Between Multiple Hyperion Instances

[Copilot]

This PR implements a Hyperion instance management feature that allows users to easily switch between multiple Hyperion instances (like HyperHDR and Hyperion.ng) without manually changing IP addresses each time.

🎯 Problem Solved

Users with multiple Hyperion instances (e.g., HyperHDR and Hyperion.ng) had to manually change IP addresses every time they wanted to switch between instances. This was tedious and error-prone.

🚀 Features Added

• Instance Dropdown: Select from saved Hyperion instances with custom names
• Add Instance: Create new instances with custom name, IP address, and port
• Edit Instance: Modify existing instance details through dialogs
• Delete Instance: Remove instances no longer needed
• Auto-populate: Address and port fields automatically fill when instance is selected
• Persistent Storage: Instances are saved in localStorage and persist across sessions

🔧 Technical Implementation

• Added instance selector dropdown above existing address field
• Used localStorage to persist instance configurations
• Auto-populates address/port when instance is selected
• Minimal changes to existing functionality (only 159 lines added)
• Full backward compatibility maintained
• All ESLint rules followed

📸 Screenshots

Main Feature UI:

Instance Switching in Action:

🎯 Usage Example

1. Click "Add" to create a new instance (e.g., "HyperHDR" with IP 192.168.1.100:19400)
2. Add another instance (e.g., "Hyperion.ng" with IP 192.168.1.101:19400)
3. Select "HyperHDR" from dropdown → Address automatically fills with 192.168.1.100:19400
4. Select "Hyperion.ng" from dropdown → Address automatically fills with 192.168.1.101:19400
5. Use "Edit" to modify instance details or "Delete" to remove instances

✅ Testing

• ✅ localStorage persistence test: PASSED
• ✅ Instance dropdown population test: PASSED
• ✅ Address auto-population test: PASSED
• ✅ Add instance functionality: PASSED
• ✅ Delete instance functionality: PASSED
• ✅ ESLint validation: PASSED
• ✅ Webpack build: PASSED

🔄 Backward Compatibility

The "Manual Entry" option remains as the default, ensuring existing workflows continue to work unchanged. Users can still manually enter IP addresses as before.

Fixes #100.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[satgit62]

I think this feature could be useful, even if not all users will necessarily use it.
Maybe we should just go ahead and implement it after all.