Offline Mode renders many Jetpack features unavailable in local development environments

### Impacted plugin

Jetpack

### Quick summary

> Currently in [Offline Mode](https://jetpack.com/redirect/?source=jetpack-support-development-mode&site=localhost:8886) (some features are disabled) because:
Your site URL is a known local development environment URL

Scary message shows up when someone is trying to use Jetpack. Let's imagine they are a new developer who likes Jetpack from WordPress.com - they've used it before.

Then, they try to install it locally and get the warning. No context.. just a message that says "This probably isn't going to work the way you want it to."

### Steps to reproduce

Install Jetpack on any local development environment

### A clear and concise description of what you expected to happen.

I'd expect users to be able to use Jetpack to do local development.

### What actually happened

Who knows? Jetpack doesn't make the user aware of what doesn't work, what can work, just throws a scary message that would deter many from not using it.

Myself included. Am I going to spend 4 hours trying to use Jetpack and it doesn't work?

### Impact

Some (< 50%)

### Available workarounds?

Yes, difficult to implement

### Platform (Simple and/or Atomic)

Simple

### Logs or notes

_No response_

No files or tests are named. Reproduce the issue by installing Jetpack on a local development environment, then trace the Offline Mode decision and warning shown to users. Done should make the limitations and supported local-development behavior clear instead of presenting an unexplained blocking message.

Written by the indexing model from the issue text.