[Repo Assist] fix: honour phpcbf.enable=false — store flag and guard format()

[github-actions]

🤖 This is an automated draft PR from Repo Assist, an AI assistant.

Summary

Fixes a bug where phpcbf.enable = false had no effect: the extension continued to spawn phpcbf even after being explicitly disabled.

Root Cause

loadSettings() used this guard:

if (!config.get("enable") === true) {
    return;
}
```

The operator precedence here is correct (`!true === true` is `false`, `!false === true` is `true`), so the early return did fire when `enable = false`. **However**, it returned *without storing the value*. `this.enable` was never set.

Then `format()` called `this.loadSettings(document.uri)`, which returned early, and immediately proceeded to spawn `phpcbf` using stale cached settings (`this.executablePath`, etc.) from a previous enabled call.

Result: toggling `phpcbf.enable = false` after the extension had already run once was a no-op.

## Fix

1. In `loadSettings()`: always read and store `this.enable = config.get("enable", true)` *before* the early return, so the flag is always current.
2. In `format()`: check `if (!this.enable) return Promise.resolve([]);` immediately after calling `loadSettings()`. This returns an empty edit list without spawning `phpcbf`.

## Test Status

All 7 existing unit tests pass:

```
✔ findFiles (7 subtests)
ℹ tests 7, pass 7, fail 0

No integration test infrastructure exists in the repo (protected package.json / vscode test harness). The fix is a straightforward guard addition and the logic is clearly correct from code inspection.

Closes

Closes #56 (phpcbf.enable setting does not disable formatting).

Generated by Repo Assist · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f