Problem

When configuring a new miner controller, there is no way to verify that the provided connection settings (IP address, port, protocol, credentials) are correct before saving it. The user only finds out whether the controller is reachable after it has been created, which makes troubleshooting misconfigurations cumbersome.

Proposed solution

Add a "Test Connection" button to the miner controller creation/edit form that validates the connectivity using the current form values, without persisting the controller.

Scope:

• The button is shown only for the PyASIC adapter type.
• The test instantiates the controller adapter from the form configuration (without saving it) and queries the device to confirm it is reachable and properly configured.
• The result is shown inline in the form (success/failure with a readable message).

Acceptance criteria

• A "Test Connection" button appears in the controller form only when the adapter type is PyASIC.
• Pressing it reports success when the device responds, and a clear error message otherwise.
• No controller is persisted as a side effect of the test.