Revert $HOME redirect in fuzz harness

With "lakebox" in manualRoots and the state-write no-op guards in place,
no path through TestCountFuzz reaches the developer's home directory:
the auto-generated workspace/account commands the fuzz exercises don't
call env.UserHomeDir, and lakebox commands aren't fuzzed at all.

The redirect was defense-in-depth, but layering test-side protection on
top of code that's already correct adds noise. Drop it; reinstate
locally if a future regression makes it useful.

Co-authored-by: Isaac

Author: pietern

cmd/fuzz_panic_test.go

@@ -14,7 +14,6 @@ import (
 	"github.com/databricks/cli/cmd"
 	"github.com/databricks/cli/libs/cmdctx"
 	"github.com/databricks/cli/libs/cmdio"
-	"github.com/databricks/cli/libs/env"
 	"github.com/databricks/cli/libs/logdiag"
 	"github.com/databricks/databricks-sdk-go"
 	"github.com/databricks/databricks-sdk-go/config"
@@ -90,10 +89,6 @@ func newFuzzHarness(t *testing.T) *fuzzHarness {
 	baseCtx = cmdctx.SetWorkspaceClient(baseCtx, wc)
 	baseCtx = cmdctx.SetAccountClient(baseCtx, ac)
 	baseCtx = cmdio.MockDiscard(baseCtx)
-	// Redirect $HOME so commands that touch state files (e.g. lakebox state at
-	// ~/.databricks/lakebox.json) can't leak writes onto the developer's
-	// machine. Any leaf reading via env.UserHomeDir(ctx) gets t.TempDir().
-	baseCtx = env.WithUserHomeDir(baseCtx, t.TempDir())
 
 	cli := cmd.New(baseCtx)