feat(providers): add Hoplite as a built-in provider

Bundle a `hoplite-provider` plugin that registers the `hoplite` provider
through the plugin SDK's ACP shim over `hoplite acp`, with the official
Hoplite mark as its icon. A narrow transformer turns Hoplite's
`_hoplite/run_phase` provisioning notifications into one in-place
"Hoplite workspace" timeline row per run.

Add Hoplite to the ACP provider catalog next to Devin, with the same
mark, so daemons without the bundled plugin can still install it over
ACP. The catalog hides the entry wherever the built-in is registered.

Document setup, project selection (`HOPLITE_PROJECT_ID`), and limits,
and add a real-provider daemon E2E that runs when `HOPLITE_E2E_CWD`
points at a repository linked to a Hoplite project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/providers.md

@@ -6,7 +6,7 @@ server integrations.
 ## Plugin providers
 
 Keep a bundled provider in `plugins/<id>/` and register it through
-`@getpaseo/plugin/server/provider`. Antigravity and Muse Code follow this pattern. Built-in loading and SDK
+`@getpaseo/plugin/server/provider`. Antigravity, Muse Code, and Hoplite follow this pattern. Built-in loading and SDK
 import rules belong to [plugins.md](plugins.md#built-in-plugins); the
 [public provider guide](../public-docs/plugins/providers.md) covers the provider contract.
 
@@ -19,6 +19,7 @@ provider icon map. You do not need a core manifest entry or provider factory.
 | ----------- | ------------------------------------------ | ---------------------------------------------------------------- |
 | Antigravity | Installed `agy` CLI                        | [Antigravity](../public-docs/supported-providers.md#antigravity) |
 | Muse Code   | MSP over one `muse serve` host per session | [Muse Code](../public-docs/muse-code.md)                         |
+| Hoplite     | ACP shim over `hoplite acp`                | [Hoplite](../public-docs/supported-providers.md#hoplite)         |
 
 ## Provider-native session options