fix(settings): remove undeclared `error`/`result` variables breaking … #4093

Originally written by @ccantynz-alt on GitHub.
Imported from https://github.com/ccantynz-alt/AlecRae.com/pull/38

…build

Two blocks in settings/page.tsx referenced error (and result) that were never declared as state, causing a TypeScript type-error that aborted the Next.js build. Removed the dead JSX — saveError already handles the profile-save error path and DangerZone has no interactive delete flow.

https://claude.ai/code/session_01XVfKC1hik1vrZhJyBV98mH

Description

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor (no functional changes)
• Documentation update
• Infrastructure / CI change

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing performed

Checklist

• My code follows the project style guidelines
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or my feature works
• New and existing tests pass locally (bun run test)
• Lint and type-check pass (bun run lint && bun run typecheck)
• I have updated documentation where necessary

Breaking changes

N/A

Screenshots

N/A