[Bug]: Object Explorer timeout should provide option to retry

### Description

The Object Explorer notification for "Failed to connect in 45 seconds" should include actionable buttons such as Retry Connection and possibly Increase Timeout.

In practice, this error most often occurs when connecting to a sleeping Azure SQL Serverless database or to a server that is temporarily disconnected. In those cases, Retry Connection is likely to be the most useful action. Increase Timeout may be less helpful, especially for serverless scenarios where the issue is not simply that the current timeout is too short.

Longer term, it would be better if we could detect sleeping Azure Serverless databases through ARM and handle that case explicitly, rather than surfacing this generic timeout error.

### Steps to Reproduce

1. Connect to sleeping serverless Azure SQL DB

Expected: No error while waking up server. Or at least a button to quickly retry connection when it fails.

Actual: Error notification that needs to be dismissed and need to retry from within OE node.

### Affected Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [x] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [ ] Other (please describe below)

### If you selected "Other", please describe the affected area

_No response_

### Environment Information

Latest

### Confirmation

- [x] I have searched existing issues and couldn't find a match
- [ ] I want to work on this issue

No files or tests are named. Start by locating the Object Explorer connection timeout notification and its connection retry flow, then verify the behavior against a sleeping Azure SQL Serverless database or temporary disconnection. Done means the timeout notification offers a usable retry action and the related behavior is covered by appropriate tests.

Written by the indexing model from the issue text.