Private network inaccessible clusters present option to create topic

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

### On what operating system are you seeing the problem?

Linux (x64)

### VS Code version

1.001

### Version of Confluent extension

1.3.0-preview

### To Reproduce

Click on an environment with private network resources
Be NOT logged into said private network
Click on the cluster in said network
See both the error message in bottom right, but also a No Topics Found content in the topic subpanel

### Current vs. Expected behavior

When being unable to reach a cluster we should prompt the user to join their private network or submit a ticket for the issue rather than ask them to create topics (which will fail if tried anyway).

### Relevant log output

```shell

```

### Which area(s) are affected? (Select all that apply)

Topics, Schemas

### Additional context

_No response_