feat: add multi-profile support for family/household use

[Kotobabi1]

Multi-Profile Support ("Family Plan")

Summary

Add support for multiple profiles in a single config file, enabling families or households to send data removal requests for all members from one Eraser installation.

Motivation

Currently Eraser supports only a single person per config file. Families wanting to protect multiple members need to maintain separate config files and run Eraser separately for each — or use a wrapper script. This PR adds native multi-profile support while maintaining full backward compatibility with existing single-profile configs.

Changes

internal/config/config.go

• Added Profiles []Profile field to Config struct (optional, omitempty)
• Added GetProfiles() method: returns profiles if set, otherwise wraps the single profile in a slice
• Added ProfileID(p Profile) helper: generates a stable "firstname-lastname" identifier for history namespacing
• Updated Validate() to validate all profiles when multiple are configured

internal/history/history.go

• Added ProfileID field to Record struct
• Added profile_id column to removal_requests table (with migration for existing DBs)
• Updated scanRecord, Add, GetLastRequestForBroker, GetRecentRequests to include profile_id
• Added GetLastRequestForBrokerAndProfile() for per-profile broker tracking
• Added GetStatsForProfile() for per-profile statistics

cmd/eraser/main.go

• Updated runSend() to iterate over all profiles, with per-profile progress output and rate-limit pauses between profiles
• Added --profile flag to send command for targeting a specific person by name
• Updated runInit() to optionally set up multiple profiles interactively
• Extracted promptProfile() helper to avoid code duplication

config.example.yaml

• Added documented profiles section showing multi-profile YAML syntax
• Added usage examples for --profile flag

Backward Compatibility

• Existing single-profile configs work unchanged — GetProfiles() falls back to the single profile field
• The profile_id column defaults to "" in the DB, so existing history records are preserved
• The web UI continues to use the first profile (multi-profile web UI would be a follow-up)

Usage

# config.yaml
profiles:
  - first_name: John
    last_name: Doe
    email: john@example.com
    country: Germany
  - first_name: Jane
    last_name: Doe
    email: jane@example.com
    country: Germany

email:
  provider: smtp
  from: privacy@example.com
  smtp:
    host: smtp.gmail.com
    port: 465
    username: privacy@example.com
    password: xxxx-xxxx-xxxx-xxxx
    use_tls: true

options:
  template: gdpr

# Send for all profiles
eraser send --dry-run

# Send for a specific person
eraser send --profile "John"
eraser send --profile "john-doe"

Future Work

• Profile switcher in the web UI dashboard
• Per-profile filtering in status command
• Per-profile inbox monitoring and response tracking